Bug 16188

Summary: AB-INT: llvm-lit: unable to find test suite for '../test'
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Mathieu Dubois-Briand <mathieu.dubois-briand>
Component: devtools / tool chainAssignee: Deepesh Varatharajan <deepesh.varatharajan>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: Medium+ CC: alex.kanavin, deepesh.varatharajan, meta.mr.watcher, meta.watcher, randy.macleod
Version: 5.99   
Target Milestone: 6.0 M3   
Hardware: x86   
OS: Multiple   
Whiteboard: AB-INT
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Mathieu Dubois-Briand 2026-03-04 12:11:40 UTC
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.
Comment 1 Mathieu Dubois-Briand 2026-03-04 12:12:45 UTC
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
Comment 2 Randy MacLeod 2026-03-05 15:42:07 UTC
Alex to reply on list.
Comment 3 Alexander Kanavin 2026-03-05 18:40:38 UTC
@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?
Comment 4 Randy MacLeod 2026-03-05 20:10:45 UTC
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 ?
Comment 5 Alexander Kanavin 2026-03-05 20:12:26 UTC
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.
Comment 6 Mathieu Dubois-Briand 2026-03-06 06:05:45 UTC
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.
Comment 7 Deepesh Varatharajan 2026-04-15 04:38:01 UTC
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.