That's a strange one... In the config step of the build, we had: Running '. ./init-build-env; bitbake-config-build disable-all-fragments' in /srv/pokybuild/yocto-worker/oe-selftest-fedora/build/build /bin/bash: line 1: ./init-build-env: No such file or directory /bin/bash: line 1: bitbake-config-build: command not found Traceback (most recent call last): File "/srv/pokybuild/yocto-worker/oe-selftest-fedora/yocto-autobuilder-helper/scripts/setup-config", line 151, in <module> disable_all_fragments() ~~~~~~~~~~~~~~~~~~~~~^^ File "/srv/pokybuild/yocto-worker/oe-selftest-fedora/yocto-autobuilder-helper/scripts/setup-config", line 75, in disable_all_fragments runcmd(cmd) ~~~~~~^^^^^ File "/srv/pokybuild/yocto-worker/oe-selftest-fedora/yocto-autobuilder-helper/scripts/setup-config", line 71, in runcmd subprocess.check_call(["/bin/bash", "-c", cmd], cwd=cmdpath) ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.13/subprocess.py", line 419, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/bin/bash', '-c', '. ./init-build-env; bitbake-config-build disable-all-fragments']' returned non-zero exit status 127.
oe-selftest-fedora opensuse160-vk-2 mathieu/master-next&master completed at 2026-08-07 11:39:59+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4312/steps/13/logs/stdio
Looking at that build (https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4312/steps/13/logs/stdio) The first failed step is "Bitbake Selftest: Write config", but that's not actually where the first error happened. In "Unpack shared repositories" I see: ERROR: Could not find oe-init-build-env in any of the layers; please use another mechanism to initialize the bitbake environment No theory yet but wanted to flag that.
We could have bitbake-setup list the head commit when it sets things up. See if it happens again.