Another new failure, display related. It might be worker specific, we will see if it does reproduce. > ERROR: core-image-minimal-1.0-r0 do_testimage: Qemu pid didn't appear in 300 seconds (04/13/26 09:55:50) > ERROR: core-image-minimal-1.0-r0 do_testimage: Status information, poll status: 0, pidfile exists: False, pidfile contents None, proc pid exists False > ERROR: core-image-minimal-1.0-r0 do_testimage: Output from runqemu: > ... > > runqemu - INFO - Host uptime: 103314.89 > > runqemu - ERROR - Failed to run qemu: qemu-system-x86_64: OpenGL is not supported by display backend 'gtk' > > runqemu - INFO - Cleaning up > runqemu - INFO - Host uptime: 103314.91 (qemu output log is empty.) In the same build, we have another failure in the bitbake extra tests step: > Running '. ./init-build-env; DISPLAY=:1 xterm -geometry 90x30 -e ${SCRIPTSDIR}/bitbake-extra-tests; exit $(cat bbextratests-exitcode)' with output to /srv/pokybuild/yocto-worker/oe-selftest-fedora/build/build/command-5-cmds.log in /srv/pokybuild/yocto-worker/oe-selftest-fedora/build/build > xterm: Xt error: Can't open display: :1 > cat: bbextratests-exitcode: No such file or directory
oe-selftest-fedora alma9-vk-2 mathieu/master-next completed at 2026-04-13 10:11:13+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3540/steps/16/logs/stdio
There was an earlier failure with what looked like a GL failure which may have taken out the vnc server, resulting in this later failure. A check on this worker showed the xserver was correctly restarted later.
oe-selftest-fedora opensuse160-vk-1 mathieu/master-next completed at 2026-04-21 09:58:31+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3585/steps/15/logs/stdio oe-selftest-fedora opensuse160-vk-1 master&master-next completed at 2026-04-22 00:16:56+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3594/steps/15/logs/stdio
oe-selftest-fedora opensuse160-vk-1 master&master-next completed at 2026-04-22 22:47:39+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3609/steps/22/logs/stdio oe-selftest-fedora opensuse160-vk-1 master&master-next completed at 2026-04-22 19:20:48+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3607/steps/22/logs/stdio oe-selftest-fedora opensuse160-vk-1 master&master-next completed at 2026-04-22 12:15:36+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3600/steps/15/logs/stdio
Test disabled on OpenSuse 16.0 https://git.openembedded.org/openembedded-core/commit/?id=be6df4679204538a8e7da287e47c0ba0515aa0dc
Issue not seen since we disabled the test as above.
Reopening: we saw that one during builds over the week-end.
oe-selftest-fedora alma10-vk-1 master-next&master completed at 2026-07-30 10:53:12+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4232/steps/15/logs/stdio oe-selftest-fedora alma10-vk-1 master-next&master completed at 2026-07-30 16:36:50+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4238/steps/15/logs/stdio oe-selftest-fedora alma10-vk-1 mathieu/master-next completed at 2026-07-31 13:11:35+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4247/steps/15/logs/stdio oe-selftest-fedora alma10-vk-1 master completed at 2026-08-01 02:41:32+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4253/steps/15/logs/stdio
This was all on alma-vk1 and it seems the X server was missing. The X server is now present.