16188 2026-03-04 12:11:40 +0000 AB-INT: llvm-lit: unable to find test suite for '../test' 2026-04-15 04:38:01 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 5.99 x86 Multiple RESOLVED NOTABUG AB-INT Medium+ normal 6.0 M3 1 mathieu.dubois-briand deepesh.varatharajan alex.kanavin deepesh.varatharajan meta.mr.watcher meta.watcher randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 104487 0 mathieu.dubois-briand 2026-03-04 12:11:40 +0000 Some new AB-INT, probably only in my branch so far. 2026-03-03 12:10:25,917 - oe-selftest - INFO - clang.LLVMSelfTestSystemEmulated.test_llvm (subunit.RemotedTestCase) 2026-03-03 12:10:25,918 - oe-selftest - INFO - ... FAIL ... 2026-03-03 12:10:25,918 - oe-selftest - INFO - 3: 1/1 9/21 (2291.61s) (0 failed) (clang.LLVMSelfTestSystemEmulated.test_llvm) 2026-03-03 12:10:25,918 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last): File "/srv/pokybuild/yocto-worker/qemux86-64-tc/build/layers/openembedded-core/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) File "/srv/pokybuild/yocto-worker/qemux86-64-tc/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/clang.py", line 185, in test_llvm raise AssertionError(f"llvm-lit failed for LLVM: {output}") AssertionError: llvm-lit failed for LLVM: llvm-lit: /srv/pokybuild/yocto-worker/qemux86-64-tc/build/build-st-1448570/tmp/work-shared/llvm-project-source-21.1.8-r1/sources/llvm-project-21.1.8.src/llvm/utils/lit/lit/discovery.py:137: warning: unable to find test suite for '../test' llvm-lit: /srv/pokybuild/yocto-worker/qemux86-64-tc/build/build-st-1448570/tmp/work-shared/llvm-project-source-21.1.8-r1/sources/llvm-project-21.1.8.src/llvm/utils/lit/lit/discovery.py:276: warning: input '../test' contained no tests error: did not discover any tests for provided path(s) I've been discussing this with Deepesh, he might come with more data. 104488 1 mathieu.dubois-briand 2026-03-04 12:12:45 +0000 qemux86-64-tc ubuntu2504-vk-1 mathieu/master-next&mathieu/master-next-tests completed at 2026-03-03 13:49:07+00:00 https://valkyrie.yocto.io/pub/non-release/20260303-71/testresults/qemux86-64-tc/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/66/builds/3322/steps/13/logs/stdio qemuarm-tc ubuntu2204-vk-3 mathieu/master-next&mathieu/master-next-tests completed at 2026-03-03 21:05:27+00:00 https://valkyrie.yocto.io/pub/non-release/20260303-86/testresults/qemuarm-tc/ https://autobuilder.yoctoproject.org/valkyrie/#/builders/42/builds/3230/steps/13/logs/stdio 104521 2 randy.macleod 2026-03-05 15:42:07 +0000 Alex to reply on list. 104543 3 alex.kanavin 2026-03-05 18:40:38 +0000 @Randy I am not familiar with this issue, and I wasn't on the triage call, so I'm not sure what I need to reply with. Did you mean someone else? 104544 4 randy.macleod 2026-03-05 20:10:45 +0000 Alex, RP mentioned that you were going to follow-up on this. I think his context was from the patch review call not the bug triage call. Does that ring a bell ? 104545 5 alex.kanavin 2026-03-05 20:12:26 +0000 Not this. I was going to follow up on https://bugzilla.yoctoproject.org/show_bug.cgi?id=16058#c72 (and did). It's a different issue. 104548 6 mathieu.dubois-briand 2026-03-06 06:05:45 +0000 Sorry, I missed that one during patch review. So this entry was kind of opened by error: the issue is only present in my branch, and what I missed at first, the failing test is a new one, only present in my branch. So this should have been handled directly on the mailing list, not on bugzilla. Said patches was submitted by Deepesh, he is aware of this. 105072 7 deepesh.varatharajan 2026-04-15 04:38:01 +0000 As this issue only affected in the testing branch and is caused by newly added test that is not present in oe-core master yet, it is not a bug. The patch series was not merged yet, and the reported problem has already been fixed. So, closing this issue accordingly.