public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <deepesh.varatharajan@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Cc: <Randy.Macleod@windriver.com>, <Sundeep.Kokkonda@windriver.com>,
	<Deepesh.Varatharajan@windriver.com>
Subject: Re: [OE-core] [PATCH V3 0/4] Oe-selftest for Clang, LLVM, LLD
Date: Wed, 04 Mar 2026 19:28:39 +0100	[thread overview]
Message-ID: <DGU7LJD9WY7B.3HPRQY4TB93YO@bootlin.com> (raw)
In-Reply-To: <20260302104314.301665-1-Deepesh.Varatharajan@windriver.com>

On Mon Mar 2, 2026 at 11:43 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.
>
> v3 changes:
> - llvm_sysroot_preprocess_testsuite function needs be added to 
>   llvm:class-target not llvm:class-nativesdk.
>
> 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.

While it runs correctly on the autobuilder, I'm noting it takes quite a
bit of time to run the tests. I'm not really against merging them, I
just want:
- to make everybody aware of that.
- to confirm with you these are some expected timings.

Taking some random build in my branch:

2026-03-03 21:20:21,805 - oe-selftest - INFO - clang.LLDSelfTestSystemEmulated.test_lld (subunit.RemotedTestCase)
2026-03-03 21:20:21,805 - oe-selftest - INFO -  ... ok
2026-03-03 21:20:21,805 - oe-selftest - INFO - 2: 1/1 18/21 (7205.57s) (0 failed) (clang.LLDSelfTestSystemEmulated.test_lld)
...
2026-03-04 00:56:44,671 - oe-selftest - INFO - clang.ClangSelfTestSystemEmulated.test_clang (subunit.RemotedTestCase)
2026-03-04 00:56:44,671 - oe-selftest - INFO -  ... ok
2026-03-04 00:56:44,671 - oe-selftest - INFO - 1: 1/1 20/21 (20188.43s) (0 failed) (clang.ClangSelfTestSystemEmulated.test_clang)
2026-03-04 01:37:34,036 - oe-selftest - INFO - clang.LLVMSelfTestSystemEmulated.test_llvm (subunit.RemotedTestCase)
2026-03-04 01:37:34,036 - oe-selftest - INFO -  ... ok
2026-03-04 01:37:34,036 - oe-selftest - INFO - 3: 1/1 21/21 (22637.80s) (0 failed) (clang.LLVMSelfTestSystemEmulated.test_llvm)

https://autobuilder.yoctoproject.org/valkyrie/#/builders/5/builds/3230

So first, we only had a few builds so far, maybe we just were a bit
unlucky (looking at the test, I believe sstate will not have any impact
in later builds). Also we already had some quite long tests in there,
but in some builds the test_clang / test_llvm really seems to take a
longer time.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2026-03-04 18:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 10:43 [PATCH V3 0/4] Oe-selftest for Clang, LLVM, LLD Deepesh.Varatharajan
2026-03-02 10:43 ` [PATCH V3 1/4] clang-tools-extra: disable tests Deepesh.Varatharajan
2026-03-02 10:43 ` [PATCH V3 2/4] clang: Use CLANG_ENABLE_TESTSUITE to enable LLVM, Clang, and LLD tests Deepesh.Varatharajan
2026-03-02 10:43 ` [PATCH V3 3/4] oeqa/selftest/clang: Add oe-seltests for Clang/LLVM/LLD Deepesh.Varatharajan
2026-03-02 10:43 ` [PATCH V3 4/4] rust: Fix rust build failure Deepesh.Varatharajan
2026-03-04 18:28 ` Mathieu Dubois-Briand [this message]
2026-03-05  6:37   ` [OE-core] [PATCH V3 0/4] Oe-selftest for Clang, LLVM, LLD Mathieu Dubois-Briand

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=DGU7LJD9WY7B.3HPRQY4TB93YO@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=Randy.Macleod@windriver.com \
    --cc=Sundeep.Kokkonda@windriver.com \
    --cc=deepesh.varatharajan@windriver.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