15698 2024-12-19 15:16:40 +0000 AB-INT: runqemu.QemuTest.test_qemu_can_shutdown hangs with "Data received serial thread" 2026-08-26 08:24:12 +0000 1 1 5 Infrastructure AutoBuilder autobuilder unspecified x86 Multiple NEW AB-INT Medium normal 6.1 1 mathieu.dubois-briand unassigned infras.ab.watcher Infras.watcher paul pidge Quan.Sun randy.macleod steve yoann.congal --- --- Done (doc changes complete) oldest_to_newest 100457 0 mathieu.dubois-briand 2024-12-19 15:16:40 +0000 106 2024-12-12 10:26:47,887 - oe-selftest - INFO - runqemu.QemuTest.test_qemu_can_shutdown (subunit.RemotedTestCase) 107 2024-12-12 10:26:47,887 - oe-selftest - INFO - ... ERROR [...] 163 runqemu - INFO - Host uptime: 221830.86 164 165 QEMU 9.1.1 monitor - type 'help' for more information 166 (qemu) 167 Waiting at most 1000 seconds for login banner (12/12/24 10:09:17) 168 Connection from 127.0.0.1:50216 169 Reached login banner in 23.90 seconds (12/12/24 10:09:40) 170 Logged in as root in serial console 171 Data received serial thread [ 172 Data received serial thread 31.39 173 Data received serial thread 7077] re 174 Data received serial thread boot: Powe 175 Data received serial thread r dow 176 Data received serial thread n 177 178 Data received serial thread 179 Data received serial thread [...] 3300 Data received serial thread 3301 WARNING: /usr/lib64/python3.12/unittest/case.py:580: RuntimeWarning: TestResult has no addDuration method 3302 warnings.warn("TestResult has no addDuration method", https://valkyrie.yoctoproject.org/#/builders/42/builds/621/steps/12/logs/stdio 100458 1 mathieu.dubois-briand 2024-12-19 15:18:13 +0000 qemuarm-tc fedora39-vk-2 mathieu/master-next completed at 2024-12-12T10:46:15Z https://valkyrie.yoctoproject.org/#/builders/42/builds/621/steps/12/logs/stdio 101813 2 randy.macleod 2025-05-01 14:07:07 +0000 Bulk move of all unassigned 5.2 medium importance bugs to 5.3. 103625 3 steve 2025-12-19 19:59:26 +0000 whinlatter https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/2791 qemux86 ubuntu2404 104010 4 paul 2026-01-21 17:10:30 +0000 This seems to be a hang when shutting down qemu. Logs say that it has shutdown but qemu has not exited. We've seen this on 32-bit ARM and x86 so far. Is there some debugging we can add to investigate the state qemu ends up in? 104939 5 randy.macleod 2026-04-02 15:16:22 +0000 A rare failure that we don't have enough info to allow us to make progress. More data and reopen if seen again. 105389 6 yoann.congal 2026-05-08 06:39:32 +0000 It happened on wrynose, reopening: qemuarm-tc rocky8-vk-1 contrib/ycongal/wrynose-nut completed at 2026-05-08 01:47:21+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/42/builds/3687 Logs: QEMU 10.2.0 monitor - type 'help' for more information (qemu) Waiting at most 1000 seconds for login banner (05/08/26 00:27:45) Connection from 127.0.0.1:36582 Reached login banner in 42.75 seconds (05/08/26 00:28:28) Logged in as root in serial console Data received serial thread [ 40. Data received serial thread 237341] reboot: Pow Data received serial thread er down Data received serial thread [...] Data received on qemu stdout b'runqemu - INFO - Cleaning up\n' Data received serial thread [...] Data received on qemu stdout b'runqemu - INFO - Host uptime: 265186.79\n\nrunqemu - INFO - Shutting down the userspace NFS server...\n' Data received serial thread [...] Data received on qemu stdout b'Getting sysroot...\n' Data received serial thread [...] 105435 7 randy.macleod 2026-05-14 14:56:31 +0000 Quan, can you work on this as well? Wouldn't it be great if your backport commit would fix this too! Test on master, backport to wrynose after review, merge, a few days soak. 106646 8 mathieu.dubois-briand 2026-08-26 08:24:12 +0000 qemuriscv64-tc opensuse160-vk-1 mathieu/master-next completed at 2026-08-25 21:55:45+00:00 https://valkyrie.yocto.io/pub/non-release/20260825-106/testresults/qemuriscv64-tc/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/58/builds/2198/steps/15/logs/stdio