https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/1271/ 020-08-21 12:33:16,813 - oe-selftest - INFO - ====================================================================== 2020-08-21 12:33:16,814 - oe-selftest - INFO - ERROR: efibootpartition.GenericEFITest.test_boot_efi (subunit.RemotedTestCase) 2020-08-21 12:33:16,814 - oe-selftest - INFO - ---------------------------------------------------------------------- 2020-08-21 12:33:16,814 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/lib/oeqa/utils/commands.py", line 344, in runqemu qemu.start(params=qemuparams, ssh=ssh, runqemuparams=runqemuparams, launch_cmd=launch_cmd, discard_writes=discard_writes) File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/lib/oeqa/targetcontrol.py", line 179, in start raise RuntimeError("%s - FAILED to start qemu - check the task log and the boot log" % self.pn) RuntimeError: core-image-minimal - FAILED to start qemu - check the task log and the boot log During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/lib/oeqa/selftest/cases/efibootpartition.py", line 45, in test_boot_efi with runqemu(self.image, ssh=False, launch_cmd=cmd) as qemu: File "/usr/lib64/python3.6/contextlib.py", line 81, in __enter__ return next(self.gen) File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/lib/oeqa/utils/commands.py", line 350, in runqemu raise Exception(msg) Exception: core-image-minimal - FAILED to start qemu - check the task log and the boot log Failed to start QEMU - see the logs in /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/testimageQemurunner log output from /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/testimage/qemurunner_log.20200821112136: INFO: rootfs file: INFO: Qemu log file: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/testimage/qemu_boot_log.20200821112136 INFO: SSH log file: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/testimage/ssh_target_log.20200821112136 DEBUG: Created listening socket for qemu serial console on: 127.0.0.1:45099 DEBUG: Created listening socket for qemu serial console on: 127.0.0.1:54679 DEBUG: launchcmd=runqemu nographic serial wic ovmf qemux86-64 tcpserial=45099:54679 bootparams="console=tty1 console=ttyS0,115200n8 printk.time=1" qemuparams="-pidfile /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/pidfile_407912" DEBUG: runqemu started, pid is 867583 DEBUG: waiting at most 120 seconds for qemu pid (08/21/20 11:21:39) DEBUG: qemu started in 3.50463604927063 seconds - qemu procces pid is 867618 (08/21/20 11:21:43) DEBUG: Target IP: None DEBUG: Server IP: None DEBUG: Starting logging thread DEBUG: Starting thread event loop DEBUG: Connection request received DEBUG: Setting connection established event DEBUG: Output from runqemu: runqemu - INFO - Running MACHINE=qemux86-64 bitbake -e ... runqemu - INFO - Continuing with the following parameters: MACHINE: [qemux86-64] FSTYPE: [wic] ROOTFS: [/home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20200821111429.rootfs.wic] OVMF: ['/home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/deploy/images/qemux86-64/ovmf.qcow2'] CONFFILE: [/home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20200821111429.qemuboot.conf] runqemu - INFO - Using preconfigured tap device tap0 runqemu - INFO - If this is not intended, touch /tmp/qemu-tap-locks/tap0.skip to make runqemu skip tap0. runqemu - INFO - Network configuration: ip=192.168.7.2::192.168.7.1:255.255.255.0 runqemu - INFO - Using scsi drive runqemu - INFO - Running /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/work/x86_64-linux/qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/qemu-system-x86_64 -device virtio-net-pci,netdev=net0,mac=52:54:00:12:34:02 -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -drive if=none,id=hd,file=/home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20200821111429.rootfs.wic,format=raw -device virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd -usb -device usb-tablet -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -drive if=pflash,format=qcow2,file=/home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/deploy/images/qemux86-64/ovmf.qcow2 -nographic -cpu core2duo -m 256 -serial tcp:127.0.0.1:45099 -serial tcp:127.0.0.1:54679 -pidfile /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/pidfile_407912 DEBUG: Waiting at most 1000 seconds for login banner (08/21/20 11:21:43) DEBUG: Connection from 127.0.0.1:58332 WARNING: Target didn't reach login banner in 1000 seconds (08/21/20 11:38:26) WARNING: Last 25 lines of text: [=3h BdsDxe: loading Boot0001 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0x4,0x0)/Scsi(0x0,0x0) BdsDxe: starting Boot0001 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0x4,0x0)/Scsi(0x0,0x0) boot Reboot Into Firmware Interface Boot in 10 sec. Boot in 10 sec. Boot in 10 sec. Boot in 10 sec. Boot in 10 sec. Boot in 10 sec. Boot in 9 sec. Boot in 9 sec. Boot in 9 sec. Boot in 9 sec. Boot in 9 sec. Boot in 9 sec. Boot in 9 sec. Boot in 9 sec. Boot in 9 sec. Boot in 9 sec. Boot in 8 sec. Boot in 8 sec. Boot in 8 sec. Boot in 8 sec. Boot in 8 sec. Boot in 8 sec. Boot in 8 sec. Boot in 8 sec. Boot in 8 sec. Boot in 8 sec. Boot in 7 sec. Boot in 7 sec. Boot in 7 sec. Boot in 7 sec. Boot in 7 sec. Boot in 7 sec. Boot in 7 sec. Boot in 7 sec. Boot in 7 sec. Boot in 7 sec. Boot in 6 sec. Boot in 6 sec. Boot in 6 sec. Boot in 6 sec. Boot in 6 sec. Boot in 6 sec. Boot in 6 sec. Boot in 6 sec. Boot in 6 sec. Boot in 6 sec. Boot in 5 sec. Boot in 5 sec. Boot in 5 sec. Boot in 5 sec. Boot in 5 sec. Boot in 5 sec. Boot in 5 sec. Boot in 5 sec. Boot in 5 sec. Boot in 5 sec. Boot in 4 sec. Boot in 4 sec. Boot in 4 sec. Boot in 4 sec. Boot in 4 sec. Boot in 4 sec. Boot in 4 sec. Boot in 4 sec. Boot in 4 sec. Boot in 4 sec. Boot in 3 sec. Boot in 3 sec. Boot in 3 sec. Boot in 3 sec. Boot in 3 sec. Boot in 3 sec. Boot in 3 sec. Boot in 3 sec. Boot in 3 sec. Boot in 3 sec. Boot in 2 sec. Boot in 2 sec. Boot in 2 sec. Boot in 2 sec. Boot in 2 sec. Boot in 2 sec. Boot in 2 sec. Boot in 2 sec. Boot in 2 sec. Boot in 2 sec. Boot in 1 sec. Boot in 1 sec. Boot in 1 sec. Boot in 1 sec. Boot in 1 sec. Boot in 1 sec. Boot in 1 sec. Boot in 1 sec. Boot in 1 sec. Boot in 1 sec. Boot in 0 sec. Boot in 0 sec. Boot in 0 sec. Boot in 0 sec. Boot in 0 sec. WARNING: Check full boot log: /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/testimage/qemu_boot_log.20200821112136 WARNING: Qemu ended unexpectedly, dump data from host is in /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-407912/tmp/log/runtime-hostdump/202008211138_qemu DEBUG: Stopping logging thread DEBUG: Stop event received DEBUG: Tearing down logging thread DEBUG: Sending SIGTERM to runqemu DEBUG: Sending SIGTERM to runqemu ======================================================================
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13799
Happened again with a failure efibootpartition.GenericEFITest.test_boot_efi on ubuntu1804-ty-3: https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1475/steps/8/logs/step2d
Chee Yang, can you take a look into this bug for the 3.3 development cycle?
tried on ubuntu 18.04.5, centos8, opensuse 15.2 and fedora 32 in VM, no luck to reproduce this.
I got this again while building gatesgarth: https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1590/steps/10/logs/step2d
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1866/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/2189/steps/15/logs/stdio oe-selftest-debian debian9-ty-2
This doesn't happen very often but we've seen it for years. Perhaps the QMP debugging will help. Chee any comments or ideas?
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/2575/steps/14/logs/stdio oe-selftest-fedora fedora33-ty-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/2970/steps/14/logs/stdio oe-selftest-fedora fedora34-ty-1
fedora35-ty-2 SSD master-next https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/3226/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/3257/steps/14/logs/stdio oe-selftest-fedora fedora35-ty-2
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/3342/steps/14/logs/stdio oe-selftest-centos centos8-ty-1
https://autobuilder.yoctoproject.org/typhoon/#builders/86/builds/3342/steps/14/logs/stdio oe-selftest-fedora fedora34-ty-1 https://autobuilder.yoctoproject.org/typhoon/#builders/79/builds/3373/steps/14/logs/stdio oe-selftest-centos centos8-ty-1
Does anyone have an idea about how to add debugging logs to gain more understanding of this bug?
Can anyone add debugging logs to gain more understanding of this bug?
Not all that frequent but it does happen a fair bit and it should be fixed sooner than other AB bugs.
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/3978/steps/14/logs/stdio Couldn't get the logs out of this one: Waiting at most 1000 seconds for login banner (08/19/22 12:32:01) Connection from 127.0.0.1:37612 Target didn't reach login banner in 1000 seconds (08/19/22 12:48:41) 2022-08-19 12:48:42,170 - oe-selftest - INFO - 7: 4/28 227/498 (1801.77s) (efibootpartition.GenericEFITest.test_boot_efi) 2022-08-19 12:48:42,170 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/oe-selftest-fedora/build/meta/lib/oeqa/utils/commands.py", line 350, in runqemu qemu.start(params=qemuparams, ssh=ssh, runqemuparams=runqemuparams, launch_cmd=launch_cmd, discard_writes=discard_writes) File "/home/pokybuild/yocto-worker/oe-selftest-fedora/build/meta/lib/oeqa/targetcontrol.py", line 172, in start start = self.runner.launch(get_ip=ssh, launch_cmd=launch_cmd, qemuparams=params) File "/home/pokybuild/yocto-worker/oe-selftest-fedora/build/meta/lib/oeqa/utils/qemurunner.py", line 490, in launch bootlog = bootlog.decode("utf-8") UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc4 in position 528: invalid continuation byte During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/oe-selftest-fedora/build/meta/lib/oeqa/selftest/cases/efibootpartition.py", line 45, in test_boot_efi with runqemu(self.image, ssh=False, launch_cmd=cmd) as qemu: File "/usr/lib64/python3.10/contextlib.py", line 135, in __enter__ return next(self.gen) File "/home/pokybuild/yocto-worker/oe-selftest-fedora/build/meta/lib/oeqa/utils/commands.py", line 356, in runqemu raise Exception(msg) Exception: 'utf-8' codec can't decode byte 0xc4 in position 528: invalid continuation byte
https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/231/steps/14/logs/stdio oe-selftest-armhost on ubuntu2004-arm-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/4240/steps/14/logs/stdio oe-selftest-ubuntu ubuntu2204-ty-2
Build move to 5.0 -- ../Randy
Bulk move from 5.0* to 5.99 to indicate that there isn't any one available to work on this issue.
We want to resolve this issue so if anyone sees the issue again, please re-open it and gather as much relevant data as you can.