From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <deepesh.varatharajan@windriver.com>,
<openembedded-core@lists.openembedded.org>
Cc: <Sundeep.Kokkonda@windriver.com>, <Deepesh.Varatharajan@windriver.com>
Subject: Re: [OE-core] [PATCH 0/3 v7] Oe-selftest for Clang, LLVM, LLD
Date: Thu, 06 Aug 2026 10:45:50 +0200 [thread overview]
Message-ID: <DKHQ9QS4ARKV.2IP7MUBX0ANXA@bootlin.com> (raw)
In-Reply-To: <20260803041741.790019-1-Deepesh.Varatharajan@windriver.com>
On Mon Aug 3, 2026 at 6:17 AM CEST, 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.
>
Hi Deepesh,
Thanks for the new series.
Can you have a run at these runs? We do have some intermittent failures:
XFAIL: LLVM :: Analysis/DDG/basic-loopnest.ll (343 of 27205)
XFAIL: LLVM :: Analysis/DependenceAnalysis/Invariant.ll (394 of 27205)
XFAIL: LLVM :: Analysis/ScalarEvolution/2008-12-14-StrideAndSigned.ll (756 of 27205)
...
198 fails on both builds, I didn't check if they are exactly the same.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/5/builds/4264
https://autobuilder.yoctoproject.org/valkyrie/#/builders/5/builds/4275
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-08-06 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 4:17 [PATCH 0/3 v7] Oe-selftest for Clang, LLVM, LLD Deepesh.Varatharajan
2026-08-03 4:17 ` [PATCH 1/3] clang-tools-extra: disable tests Deepesh.Varatharajan
2026-08-03 4:17 ` [PATCH 2/3] clang: Enable cmake flags for llvm, clang, lld tests Deepesh.Varatharajan
2026-08-03 4:17 ` [PATCH 3/3] oeqa/selftest/clang: Add oe-selftests for Clang/LLVM/LLD test suites Deepesh.Varatharajan
2026-08-06 11:40 ` [OE-core] " Ross Burton
2026-08-06 8:45 ` Mathieu Dubois-Briand [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=DKHQ9QS4ARKV.2IP7MUBX0ANXA@bootlin.com \
--to=mathieu.dubois-briand@bootlin.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