kirkstone qemumips-alt ubuntu2404-vk-3 https://autobuilder.yoctoproject.org/valkyrie/#/builders/13/builds/1417/steps/13/logs/stdio Maybe linked to #13631? Log extract: NOTE: recipe core-image-sato-sdk-1.0-r0: task do_testimage: Started QMP Available for connection at /srv/pokybuild/yocto-worker/qemumips-alt/build/build/tmp/.l_n7q2lp QMP connected to QEMU at 01/15/26 00:42:25 and took 2.3907694816589355 seconds NOTE: Pressure status changed to CPU: False, IO: False, Mem: None (CPU: 3779.4/10000.0, IO: 323.9/10000.0, Mem: 3851.4/None) - using 1/16 bitbake threads NOTE: Running task 1086 of 1087 (/srv/pokybuild/yocto-worker/qemumips-alt/build/meta/recipes-sato/images/core-image-sato.bb:do_testimage) NOTE: Running task 1087 of 1087 (/srv/pokybuild/yocto-worker/qemumips-alt/build/meta/recipes-extended/images/core-image-full-cmdline.bb:do_testimage) NOTE: recipe core-image-sato-1.0-r0: task do_testimage: Started NOTE: recipe core-image-full-cmdline-1.0-r0: task do_testimage: Started QMP released QEMU at 01/15/26 00:42:26 and took 0.4255251884460449 seconds from connect QMP Available for connection at /srv/pokybuild/yocto-worker/qemumips-alt/build/build/tmp/.9dm4nvgr QMP Available for connection at /srv/pokybuild/yocto-worker/qemumips-alt/build/build/tmp/.y8mxelat QMP connected to QEMU at 01/15/26 00:42:28 and took 1.2016816139221191 seconds QMP released QEMU at 01/15/26 00:42:28 and took 0.2482752799987793 seconds from connect QMP connected to QEMU at 01/15/26 00:42:29 and took 2.0793356895446777 seconds QMP released QEMU at 01/15/26 00:42:29 and took 0.24218988418579102 seconds from connect Started HTTPService on 0.0.0.0:44373 Test requires apt to be installed Stopped HTTPService on 0.0.0.0:44373 Started HTTPService on 0.0.0.0:35993 Test requires apt to be installed Stopped HTTPService on 0.0.0.0:35993 Started HTTPService on 0.0.0.0:37145 Test requires apt to be installed Stopped HTTPService on 0.0.0.0:37145 Traceback (most recent call last): File "/srv/pokybuild/yocto-worker/qemumips-alt/build/meta/lib/oeqa/runtime/cases/ping.py", line 21, in test_ping output += proc.communicate()[0].decode('utf-8') ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/subprocess.py", line 1196, in communicate stdout = self.stdout.read() ^^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/qemumips-alt/build/meta/lib/oeqa/core/decorator/oetimeout.py", line 18, in _timeoutHandler raise OEQATimeoutError("Timed out after %s " oeqa.core.exception.OEQATimeoutError: Timed out after 30 seconds of execution During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/srv/pokybuild/yocto-worker/qemumips-alt/build/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/qemumips-alt/build/meta/lib/oeqa/runtime/cases/ping.py", line 27, in test_ping self.fail("Ping timeout error for address %s, count %s, output: %s" % (self.target.ip, count, output)) AssertionError: Ping timeout error for address 192.168.7.8, count 0, output: PING 192.168.7.8 (192.168.7.8) 56(84) bytes of data. --- 192.168.7.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms PING 192.168.7.8 (192.168.7.8) 56(84) bytes of data. --- 192.168.7.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms Test case ssh.SSHTest.test_ssh depends on ping.PingTest.test_ping but it didn't pass/run.
It is intermittent: the rebuild succeeded : https://autobuilder.yoctoproject.org/valkyrie/#/builders/13/builds/1418
Created attachment 5172 [details] log.testimage from https://autobuilder.yoctoproject.org/valkyrie/#/builders/13/builds/1417
Created attachment 5173 [details] qemu_boot_log from https://autobuilder.yoctoproject.org/valkyrie/#/builders/13/builds/1417
> Maybe linked to #13631? Does not seem like it: qemu boot log does go to the login banner.
Related master commit: oeqa/runtime: Add debugging if networking fails - openembedded-core - OpenEmbedded Core layer https://git.openembedded.org/openembedded-core/commit/?id=3291f9d07ecfe7d3301dc914f5e6a80577cf1d5d => Maybe backport it?
Kirkstone is no longer maintained