16170 2026-02-12 12:18:08 +0000 yocto-check-layer: test never ends on broken layers 2026-02-19 15:42:39 +0000 1 1 10 QA/Testing Tooling tooling unspecified x86 Multiple RESOLVED FIXED High normal 6.0 M3 1 mathieu.dubois-briand tim.orling bruce.ashfield paul randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 104245 0 mathieu.dubois-briand 2026-02-12 12:18:08 +0000 In some conditions, yocto-check-layer common.CommonCheckLayer.test_signatures test never finishes or at least not in a reasonable amount of time. This is seen on the autobuilder with meta-virtualization: > INFO: test_signatures (common.CommonCheckLayer) > > command timed out: 16200 seconds without output running [b'/srv/pokybuild/yocto-worker/check-layer-nightly/yocto-autobuilder-helper/scripts/run-config', b'check-layer-nightly', b'/srv/pokybuild/yocto-worker/check-layer-nightly/build/build', b'master', b'ssh://git@push.yoctoproject.org/poky', b'--sstateprefix', b'', b'--buildappsrcrev', b'', b'--publish-dir', b'', b'--build-type', b'quick', b'--workername', b'debian11-vk-1', b'--build-url', b'https://autobuilder.yoctoproject.org/valkyrie/#/builders/85/builds/976', b'--results-dir', b'/srv/autobuilder/valkyrie.yocto.io/pub/non-release/20260211-3/testresults', b'--quietlogging', b'--stepname', b'cmds', b'--phase', b'7'], attempting to kill > process killed by signal 9 But it can also easily be reproduced locally with: > yocto-check-layer-wrapper ../meta-virtualization --dependency ../meta-openembedded/meta-oe ../meta-openembedded/meta-networking ../meta-openembedded/meta-python ../meta-openembedded/meta-filesystems --no-auto-dependency We know that current master branch on meta-virtualization is broken, but yocto-check-layer should still report errors instead of being stuck. Breaking commit in meta-virtualization: https://git.yoctoproject.org/meta-virtualization/commit/?id=6f53d7763906f24d86e89da4da744421c52d591c Code is stuck get_depgraph() while waiting for tifoil to finish running the "generateDepTreeEvent" command. I added some traces: we are receiving events, but none allowing to get out of the "while" loop. https://git.openembedded.org/openembedded-core/tree/scripts/lib/checklayer/__init__.py#n367 Looking at bitbake-cookerdaemon.log, it looks like the command did finish and some reply was sent. So probably some logic is wrong somewhere in interpreting this rely. > 2149754 13:14:50.133747 Running command ['generateDepTreeEvent', ['world'], 'do_build'] > 2149754 13:14:50.133787 Registering idle function <bound method Command.runAsyncCommand of <bb.command.Command object at 0x7f66dfe61fd0>> > 2149754 13:14:50.133794 Sending reply (True, None) > 2149754 13:14:50.133827 Command Completed (socket: True) > 2149754 13:14:51.133844 Parsing completed > 2149754 13:14:52.380348 Removing idle function <bound method Command.runAsyncCommand of <bb.command.Command object at 0x7f66dfe61fd0>> at idleFinish Stopping investigations here for now. 104246 1 mathieu.dubois-briand 2026-02-12 12:19:18 +0000 check-layer-nightly debian11-vk-1 master completed at 2026-02-11 06:49:50+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/85/builds/976/steps/24/logs/stdio check-layer-nightly debian13-vk-1 master completed at 2026-02-12 05:29:53+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/85/builds/977/steps/24/logs/stdio 104260 2 randy.macleod 2026-02-12 15:51:33 +0000 Two issues: 1. meta-virt should pass (M+) 2. yocto-check-layer should not hang (High). 104265 3 bruce.ashfield 2026-02-12 16:13:14 +0000 FWIW. I'm seeing the same thing on my local runs, it hangs at the same point and never continues. Whether I use the wrapper, the tool directly, etc, has no impact. But I can run the bitbake commands directly and they complete in the expected amount of time. I found there were some pipe and other issues and maybe a timetout involved, but ran out of time to debug it. 104308 4 tim.orling 2026-02-15 20:41:52 +0000 I have a proposed fix: https://git.openembedded.org/openembedded-core-contrib/log/?h=timo/checklayer-16170 Pending the outcome of a test run: https://autobuilder.yoctoproject.org/valkyrie/#/builders/85/builds/986 104309 5 tim.orling 2026-02-15 22:12:59 +0000 https://lists.openembedded.org/g/openembedded-core/message/231171 104312 6 mathieu.dubois-briand 2026-02-16 11:47:27 +0000 check-layer-nightly debian12-vk-7 master completed at 2026-02-13 05:30:23+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/85/builds/980/steps/24/logs/stdio check-layer-nightly ubuntu2204-vk-4 master completed at 2026-02-14 05:40:47+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/85/builds/982/steps/24/logs/stdio check-layer-nightly debian12-vk-7 master completed at 2026-02-15 05:30:19+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/85/builds/983/steps/24/logs/stdio check-layer-nightly ubuntu2404-vk-2 master completed at 2026-02-16 05:33:27+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/85/builds/987/steps/24/logs/stdio 104340 7 tim.orling 2026-02-17 23:01:49 +0000 These most recent runs are without my patch applied. 104343 8 mathieu.dubois-briand 2026-02-19 08:38:34 +0000 The patch is still not applied on master, so following failures are expected: check-layer-nightly fedora40-vk-4 master completed at 2026-02-19 05:38:38+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/85/builds/993/steps/24/logs/stdio check-layer-nightly debian12-vk-5 master completed at 2026-02-17 05:30:27+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/85/builds/990/steps/24/logs/stdio check-layer-nightly rocky9-vk-1 master completed at 2026-02-18 08:23:18+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/85/builds/992/steps/24/logs/stdio 104349 9 tim.orling 2026-02-19 15:42:39 +0000 Merged: https://git.openembedded.org/openembedded-core/commit/?id=a2c6bf582287a56ae241499598d3038b3c3cdb4f