From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ross.burton@arm.com>, <openembedded-core@lists.openembedded.org>
Cc: "Michael Halstead" <mhalstead@linuxfoundation.org>
Subject: Re: [OE-core] [PATCH 1/6] clang: improve opt-viewer PACKAGECONFIG
Date: Sun, 14 Sep 2025 19:42:25 +0200 [thread overview]
Message-ID: <DCSPIZJJ55W2.PI9LL2D5W0XX@bootlin.com> (raw)
In-Reply-To: <20250912143038.3345369-1-ross.burton@arm.com>
On Fri Sep 12, 2025 at 4:30 PM CEST, Ross Burton via lists.openembedded.org wrote:
> Instead of patching the python module detection, we can use the hidden
> option LLVM_TOOL_OPT_VIEWER_BUILD.
>
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
Hi Ross,
I took this series, but it resulted in a lot of OOM failures during the
reproducibility test build:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2484
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2485
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2487
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2489
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2486
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2488
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2491
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2493
Some of these do reports errors in ovmf_git.bb:do_deploy, I wonder if
this is somehow related.
Michael Halstead has some traces from the OOM killer, at least for one
occurrence. I will forward you the mail he sent about these, maybe there
is any useful data in there.
Also, one build completed (to a failure). Maybe just some luck in job
ordering, so it failed before it had the opportunity to crash. It
contains errors for both ovmf and ffmpeg builds:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/2492
Also this same build does report some reproducibility issues on clang,
llvm and others:
http://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20250914-qe46no4m/packages/diff-html/
So, I believe this might a bit difficult to debug, please tell me if I
can help you in any way.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-09-14 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 14:30 [PATCH 1/6] clang: improve opt-viewer PACKAGECONFIG Ross Burton
2025-09-12 14:30 ` [PATCH 2/6] clang: disable all test targets Ross Burton
2025-09-15 5:14 ` [OE-core] " Khem Raj
2025-09-15 9:39 ` Ross Burton
2025-09-12 14:30 ` [PATCH 3/6] clang: add option for llvm-exegesis Ross Burton
2025-09-12 14:30 ` [PATCH 4/6] clang: remove obsolete install steps Ross Burton
2025-09-12 14:30 ` [PATCH 5/6] llvm: add recipe for just the LLVM libraries Ross Burton
2025-09-12 14:30 ` [PATCH 6/6] clang: use llvm recipe Ross Burton
2025-09-14 17:42 ` 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=DCSPIZJJ55W2.PI9LL2D5W0XX@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=mhalstead@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.