16001 2025-10-13 12:08:55 +0000 AB-INT: oe-selftest-armhost: Failed to start QEMU 2025-10-16 14:48:01 +0000 1 1 10 QA/Testing Runtime Testing oeqa/runtime unspecified x86 Multiple RESOLVED INVALID AB-INT Medium+ normal 5.3 M4 1 mathieu.dubois-briand unassigned randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 102920 0 mathieu.dubois-briand 2025-10-13 12:08:55 +0000 Two different fails on two different tests. I still hope they are somehow related... The first one seems to be just slow, as it reached Multi-User before the time-out: Starting Sample application start-up unit... [ OK ] Finished Sample application start-up unit. [ OK ] Started User Login Management. [ OK ] Started D-Bus System Message Bus. [ OK ] Reached target Multi-User System. The second one is maybe a worse one: [ 1.094628] [drm] pci: virtio-gpu-pci detected at 0000:00:06.0 [ 1.094711] [drm] features: -virgl +edid -resource_blob -host_visible [ 1.094713] [drm] features: -context_init [ 1.095166] [drm] number of scanouts: 1 [ 1.095171] [drm] number of cap sets: 0 [ 1.100504] printk: legacy console [hvc0] enabled [ 1.108542] [drm] Initialized virtio_gpu 0.1.0 for 0000:00:06.0 on minor 0 [ 1.134901] Console: switching to colour frame buffer device 160x50 I will continue monitor these and create dedicated tickets if it makes sense. 102921 1 mathieu.dubois-briand 2025-10-13 12:10:43 +0000 oe-selftest-armhost ubuntu2404-vk-arm2 master-next completed at 2025-10-07 23:53:31+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/2648/steps/15/logs/stdio oe-selftest-armhost ubuntu2204-vk-arm1 mathieu/master-next completed at 2025-10-12 12:16:51+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/2672/steps/15/logs/stdio 102959 2 randy.macleod 2025-10-16 14:48:01 +0000 Second issue is related to a PATCH level update to qemu-10.1.1 in Mathieu's master-next branch and so we will not take the update into master. The first issue will be tracked by a separate bug.