Bug 16393

Summary: AB-INT: ./init-build-env: No such file or directory
Product: [Infrastructure] AutoBuilder Reporter: Mathieu Dubois-Briand <mathieu.dubois-briand>
Component: autobuilderAssignee: Unassigned <unassigned>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Medium CC: infras.ab.watcher, Infras.watcher, paul, randy.macleod
Version: unspecified   
Target Milestone: 6.1   
Hardware: x86   
OS: Multiple   
Whiteboard: AB-INT
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Mathieu Dubois-Briand 2026-08-11 14:41:49 UTC
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.
Comment 1 Mathieu Dubois-Briand 2026-08-11 14:54:48 UTC
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
Comment 2 Paul Barker 2026-08-11 16:09:34 UTC
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.
Comment 3 Randy MacLeod 2026-08-13 14:38:33 UTC
We could have bitbake-setup list the head commit when it sets things up.
See if it happens again.