FreeBSD-main-amd64-test - Build #26061 - Still Failing

From: <jenkins-admin_at_FreeBSD.org>
Date: Sun, 02 Mar 2025 16:55:39 UTC
FreeBSD-main-amd64-test - Build #26061 (e8a5b9fd73f4f437a03c85e7644daa55652e224b) - Still Failing

Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/26061/
Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/26061/changes
Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/26061/console

Status explanation:
"Failure" - the build is suspected being broken by the following changes
"Still Failing" - the build has not been fixed by the following changes and
                  this is a notification to note that these changes have
                  not been fully tested by the CI system

Change summaries:
(Those commits are likely but not certainly responsible)

e8a5b9fd73f4f437a03c85e7644daa55652e224b by dfr:
release: build OCI images with shell scripts



The end of the build log:

Started by upstream project "FreeBSD-main-amd64-testvm" build number 29220
originally caused by:
 Started by upstream project "FreeBSD-main-amd64-build" build number 31364
 originally caused by:
  Started by an SCM change
  Started by an SCM change
  Started by an SCM change
  Started by an SCM change
  Started by an SCM change
  Started by an SCM change
  Started by an SCM change
  Started by an SCM change
  Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Injecting as environment variables the properties content 
LINK_TYPE=latest_tested
FBSD_TARGET_ARCH=amd64
FBSD_TARGET=amd64
FBSD_BRANCH=main

[EnvInject] - Variables injected successfully.
[EnvInject] - Injecting contributions.
Building remotely on lancelot.nyi.freebsd.org (vmhost_qemu vmhost_bhyve vmhost_bhyve_fast image_builder) in workspace /jenkins/workspace/FreeBSD-main-amd64-test
The recommended git tool is: NONE
No credentials specified
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://git.freebsd.org/src.git
 > git init /jenkins/workspace/FreeBSD-main-amd64-test/src # timeout=10
Using reference repository: /home/git/src.git
Fetching upstream changes from https://git.freebsd.org/src.git
 > git --version # timeout=10
 > git --version # 'git version 2.46.2'
 > git fetch --tags --force --progress -- https://git.freebsd.org/src.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://git.freebsd.org/src.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision e8a5b9fd73f4f437a03c85e7644daa55652e224b (refs/remotes/origin/main)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e8a5b9fd73f4f437a03c85e7644daa55652e224b # timeout=10
Commit message: "release: build OCI images with shell scripts"
 > git rev-list --no-walk 3ae7c763540afc0bc5320eb45f2661d315370eb8 # timeout=10
Checking for pre-build
Executing pre-build step
Checking if email needs to be generated
No emails were triggered.
Checking for pre-build
Executing pre-build step
Checking if email needs to be generated
No emails were triggered.
Checking for pre-build
Executing pre-build step
Checking if email needs to be generated
No emails were triggered.
[FreeBSD-main-amd64-test] $ /bin/sh -xe /tmp/jenkins6997977255727856256.sh
+ rm -fr freebsd-ci
+ git clone '--depth=1' --single-branch -b main https://github.com/freebsd/freebsd-ci.git
Cloning into 'freebsd-ci'...
+ cd freebsd-ci
+ git rev-parse HEAD
476c8808803a47344a47adfe9573345cceb14fce
+ cd ..
[FreeBSD-main-amd64-test] $ /bin/sh -xe /tmp/jenkins17507572505393354896.sh
+ sh -ex 'freebsd-ci/jobs/$/build.sh'
sh: cannot open freebsd-ci/jobs/$/build.sh: No such file or directory
Build step 'Execute shell' marked build as failure
[PostBuildScript] - [INFO] Executing post build scripts.
[PostBuildScript] - [INFO] Build does not have any of the results [SUCCESS]. Did not execute build step #0.
Recording test results
[Checks API] No suitable checks publisher found.
Checking for post-build
Performing post-build step
Checking if email needs to be generated
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Sending mail from default account using System Admin e-mail address