From: Deepesh Varatharajan <deepesh.varatharajan@windriver.com>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
openembedded-core@lists.openembedded.org
Cc: Randy.Macleod@windriver.com, Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [PATCH 0/4 V2] Oe-selftest for Clang, LLVM, LLD
Date: Mon, 2 Mar 2026 16:22:56 +0530 [thread overview]
Message-ID: <6ce93caf-d418-49ca-b55d-087c3b6ec07d@windriver.com> (raw)
In-Reply-To: <DGS8JWNFLTW8.3E7NT6B8E8GNP@bootlin.com>
On 02-03-2026 16:18, Mathieu Dubois-Briand wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Mon Mar 2, 2026 at 7:49 AM CET, Deepesh via lists.openembedded.org Varatharajan wrote:
>> From: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
>>
>> This patch series introduces a test framework to run selftests for
>> target builds of Clang, LLVM, and LLD.
>>
>> v2 changes:
>> - Enable required CMake flags only when running the testsuite.
>> - Ensure default build time and package sizes remain unaffected.
>>
>> Summary of changes:
>> -Patch 1: Disable clang-tools-extra tests, as Clang's CMake cannot
>> detect the llvm-bcanalyzer target.
>> -Patch 2: Enabled the necessary CMake flags for clang, llvm & lld tests
>> when CLANG_ENABLE_TESTSUITE is set to "1".
>> -Patch 3: Selftest script for Clang, LLVM, and LLD including exclude list
>> -Patch 4: Fix rust build failure by replacing target llvm-config with native
>>
> Hi Deepesh,
>
> Thanks for the new version, but it looks like we now have some failing
> tests:
>
> 2026-03-02 09:52:32,943 - oe-selftest - INFO - clang.ClangSelfTestSystemEmulated.test_clang (subunit.RemotedTestCase)
> 2026-03-02 09:52:32,943 - oe-selftest - INFO - ... FAIL
> ...
> AssertionError: llvm-lit failed for Clang: llvm-lit: /srv/pokybuild/yocto-worker/qemuarm-tc/build/build-st-3082983/tmp/work-shared/llvm-project-source-21.1.8-r1/sources/llvm-project-21.1.8.src/llvm/utils/lit/lit/llvm/subst.py:133: fatal: Did not find FileCheck in /srv/pokybuild/yocto-worker/qemuarm-tc/build/build-st-3082983/tmp/work/cortexa15t2hf-neon-poky-linux-gnueabi/clang/21.1.8/recipe-sysroot/usr/bin
> ...
> 2026-03-02 09:54:51,485 - oe-selftest - INFO - clang.LLVMSelfTestSystemEmulated.test_llvm (subunit.RemotedTestCase)
> 2026-03-02 09:54:51,485 - oe-selftest - INFO - ... FAIL
> ...
> 2026-03-02 09:55:49,997 - oe-selftest - INFO - clang.LLDSelfTestSystemEmulated.test_lld (subunit.RemotedTestCase)
> 2026-03-02 09:55:49,997 - oe-selftest - INFO - ... FAIL
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/42/builds/3224
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/5/builds/3222
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/58/builds/1118
>
> Can you have a look at these?
Hi Mathieu,
Thanks for pointing this out. I’ve already sent a V3 of this patch that
addresses this issue.
Regards,
Deepesh
>
> Thanks,
> Mathieu
>
> --
> Mathieu Dubois-Briand, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
prev parent reply other threads:[~2026-03-02 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 6:49 [PATCH 0/4 V2] Oe-selftest for Clang, LLVM, LLD Deepesh.Varatharajan
2026-03-02 6:49 ` [PATCH 1/4 V2] clang-tools-extra: disable tests Deepesh.Varatharajan
2026-03-02 6:49 ` [PATCH 2/4 V2] clang: Use CLANG_ENABLE_TESTSUITE to enable LLVM, Clang, and LLD tests Deepesh.Varatharajan
2026-03-02 6:49 ` [PATCH 3/4 V2] oeqa/selftest/clang: Add oe-seltests for Clang/LLVM/LLD Deepesh.Varatharajan
2026-03-02 6:49 ` [PATCH 4/4 V2] rust: Fix rust build failure Deepesh.Varatharajan
2026-03-02 10:32 ` [PATCH 0/4 V2] Oe-selftest for Clang, LLVM, LLD Deepesh Varatharajan
2026-03-02 10:48 ` [OE-core] " Mathieu Dubois-Briand
2026-03-02 10:52 ` Deepesh Varatharajan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ce93caf-d418-49ca-b55d-087c3b6ec07d@windriver.com \
--to=deepesh.varatharajan@windriver.com \
--cc=Randy.Macleod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox