It might be a new AB-INT or related with recent autobuilder issues. ERROR: core-image-ptest-python3-1.0-r0 do_testimage: runqemu exited with code 1 ERROR: core-image-ptest-python3-1.0-r0 do_testimage: Output from runqemu: runqemu - INFO - Decompressing /srv/pokybuild/yocto-worker/qemux86-64-musl-ptest/build/build/tmp/deploy/images/qemux86-64/core-image-ptest-python3-qemux86-64.rootfs.ext4.zst to /srv/pokybuild/yocto-worker/qemux86-64-musl-ptest/build/build/tmp/deploy/images/qemux86-64/core-image-ptest-python3-qemux86-64.rootfs-20260320144231.ext4 /srv/pokybuild/yocto-worker/qemux86-64-musl-ptest/build/build/tmp/deploy/images/qemux86-64/core-image-ptest-python3-qemux86-64.rootfs-20260320144231.ext4.zst: 801783808 bytes runqemu - INFO - Continuing with the following parameters: KERNEL: [/srv/pokybuild/yocto-worker/qemux86-64-musl-ptest/build/build/tmp/deploy/images/qemux86-64/bzImage] MACHINE: [qemux86-64] FSTYPE: [ext4] ROOTFS: [/srv/pokybuild/yocto-worker/qemux86-64-musl-ptest/build/build/tmp/deploy/images/qemux86-64/core-image-ptest-python3-qemux86-64.rootfs-20260320144231.ext4] SNAPSHOT: [Enabled. Changes on rootfs won't be kept after QEMU shutdown.] CONFFILE: [/srv/pokybuild/yocto-worker/qemux86-64-musl-ptest/build/build/tmp/deploy/images/qemux86-64/core-image-ptest-python3-qemux86-64.rootfs.qemuboot.conf] runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap1.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap2.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap3.lock failed: [Errno 11] Resource temporarily unavailable runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap4.lock failed: [Errno 11] Resource temporarily unavailable ... runqemu - ERROR - Error: There are no available tap devices to use for networking, runqemu - ERROR - and I see /etc/runqemu-nosudo exists, so I am not going to try creating runqemu - ERROR - a new one with sudo. runqemu - INFO - Cleaning up runqemu - INFO - Host uptime: 258778.60
qemux86-64-musl-ptest debian12-vk-1 master&master-next completed at 2026-03-20 16:47:11+00:00 https://valkyrie.yocto.io/pub/non-release/20260320-80/testresults/qemux86-64-musl-ptest/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/123/steps/13/logs/stdio qemux86-64-ptest debian12-vk-1 master&master-next completed at 2026-03-20 16:45:28+00:00 https://valkyrie.yocto.io/pub/non-release/20260320-80/testresults/qemux86-64-ptest/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3340/steps/13/logs/stdio
Likely a bad combination of infrastructure probelms, Yoann thinks this happened just before the NFS problems. Re-open if seen again.