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

FreeBSD-main-amd64-test - Build #26053 (e74a3c75855ffae028bd1991c73dee474aafce05) - Still Failing

Build information: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/26053/
Full change log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/26053/changes
Full build log: https://ci.FreeBSD.org/job/FreeBSD-main-amd64-test/26053/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)

43fa7b907e9cc5ce365afd05775349d199fc2eb4 by kib:
amdiommu: add register definitions from IOMMU spec 48882 rev. 3.10

4b86550923cfb226a65b7d48c661654bd0a240cc by adrian:
ifconfig: add AES-GCMP RSN OUI decoding

e74a3c75855ffae028bd1991c73dee474aafce05 by adrian:
net80211: add AES-GCM in ddb output



The end of the build log:

Started by upstream project "FreeBSD-main-amd64-testvm" build number 29212
originally caused by:
 Started by upstream project "FreeBSD-main-amd64-build" build number 31356
 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
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 e74a3c75855ffae028bd1991c73dee474aafce05 (refs/remotes/origin/main)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e74a3c75855ffae028bd1991c73dee474aafce05 # timeout=10
Commit message: "net80211: add AES-GCM in ddb output"
 > git rev-list --no-walk 10c633ab1204e13d6fbad9f0f474229eed5fd280 # 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/jenkins7488654236999746598.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/jenkins7295433793528093797.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