https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5897/steps/14/logs/stdio oe-selftest-centos on alma9-ty-1 The stdio log shows: NOTE: No reply from server in 30s (for command ping at 12:23:12.994729) Timeout while waiting for a reply from the bitbake server (60s at 12:23:43.095454) AAlso from the stdio log: AssertionError: Command 'bitbake virtual/kernel' returned non-zero exit status 1: Similar to https://bugzilla.yoctoproject.org/show_bug.cgi?id=15043 but likely unrelated. It would be useful to have the bitbake-cookerdaemon.log file, but for this instance it is gone.
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5922/steps/14/logs/stdio which had https://autobuilder.yocto.io/pub/failed-builds-data/bitbake-timeout2/bitbake-cookerdaemon.log
https://autobuilder.yoctoproject.org/typhoon/#/builders/97/builds/7509/steps/10/logs/stdio qemuarm64-armhost ubuntu2204-arm-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/97/builds/7505/steps/10/logs/stdio qemuarm64-armhost ubuntu2204-arm-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/6572/steps/14/logs/stdio oe-selftest-centos alma9-ty-2 NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection (#8)... (Traceback (most recent call last): File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/bitbake/lib/bb/main.py", line 489, in setup_bitbake server_connection = bb.server.process.connectProcessServer(sockname, featureset) File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/bitbake/lib/bb/server/process.py", line 708, in connectProcessServer sock.connect(os.path.basename(sockname)) BlockingIOError: [Errno 11] Resource temporarily unavailable , 19:53:24.849271)
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/6391/steps/14/logs/stdio oe-selftest-centos alma9-ty-2
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/6670/steps/11/logs/stdio qemuarm64-ptest ubuntu2004-arm-1 The error messages in the bottom of the stdio may not be precisely the same, but it is still a timeout issue.
https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/3816/steps/14/logs/stdio oe-selftest-armhost ubuntu2204-arm-1
https://autobuilder.yoctoproject.org/typhoon/#/builders/97/builds/8751/steps/10/logs/stdio qemuarm64-armhost on ubuntu2204-arm-1
oe-selftest-debian debian11-ty-1 Error talking to server: Connection closed https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/6586/steps/11/logs/stdio Timeout while waiting for a reply from the bitbake server (60s at 03:22:37.188037) https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/7022/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/97/builds/8684/steps/10/logs/stdio
oe-selftest fedora38-ty-6 https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/2669/steps/14/logs/stdio
oe-selftest-fedora fedora41-vk-1 https://valkyrie.yoctoproject.org//#/builders/48/builds/185/steps/14/logs/stdio Richard saved some data: https://valkyrie.yocto.io/pub/shared-failure-data/fedora41-vk-1-selftest/ 12:43 < RP> mathieudb: the key message in cookerdaemon is "Idle loop didn't finish queued commands after 30s, exiting." 12:43 < RP> in there twice 12:43 * RP is hoping there are timestamps in the json log
oe-selftest-fedora fedora41-vk-1 https://valkyrie.yoctoproject.org/#/builders/48/builds/192 Thanks Richard, again: https://valkyrie.yocto.io/pub/shared-failure-data/fedora41-vk-1-selftest/2/
oe-selftest-fedora fedora41-vk-1 https://valkyrie.yoctoproject.org/#/builders/48/builds/279/steps/14/logs/stdio
Not seen in YP for ~6 months. Shall we declare this fixed ? YP does have the new, faster cluster. This is still seen in WR Linux, where we have: - a slow template bitbake patch and - we overload our container-based builds. We have not had a customer report the issue.
There were some timeout-related commits but I can't find them... WR still has some timeouts but that's their problem since they have a slow template feature and overloaded builders!