From: "Dora, Sunil Kumar" <SunilKumar.Dora@windriver.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Areas we could do with assistance
Date: Thu, 10 Sep 2026 13:25:46 +0000 [thread overview]
Message-ID: <2fcf2fd1-9daf-409b-9bd3-8b9168044a1a@windriver.com> (raw)
In-Reply-To: <db81c3f01f75899c8eed72fbfe8776321572e3c9.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 3311 bytes --]
On 9/9/2026 4:02 PM, Richard Purdie via lists.openembedded.org 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.
Hi Everyone,
There are a few areas we could do with some help at the moment:
a) ptest in util-linux failing for qemuriscv64:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2369
b) Finding better tests for the github related bitbake-selftests. I've
made good progress at removing github.com references from
https://git.openembedded.org/bitbake/tree/lib/bb/tests/fetch.py but
some still remain. I also have not rewritten all the submodules to not
use github for the underlying submodules in all cases. The ones that
are left are:
test_gomod_url
test_gomod_url_go_mod_only
test_gomodgit_url_subdir
test_git_submodule_iotedge
You can also now see timing data on:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4848/steps/14/logs/stdio
and help with speeding any of these up would also be welcome!
c) The xserver startup issues:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13908
d) Reproducibility on x86 vs arm hosts. Alejandro has made good
progress with identifying many of the rust related issues but there are
some non-rust issues remaining. One key set of diffs are these:
https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260908-sv8uww77/packages/diff-html/
Particularly the perl issue, the locale change and numpy config issues.
Any help on these welcome, just let us know if you're working on
anything to avoid duplication.
Hi Richard,
On point (d), just to avoid duplicating work: I’ve been looking into the x86 vs. ARM host reproducibility failures for some time now,
mainly around the Rust and Git issues.
For rust/rust-dbg, the remaining diff after the SVH work appears to be caused by the build path leaking into object file names
during the Rust build. I have a fairly good understanding of the issue now and am validating a fix locally.
Once confirmed, I’ll post the analysis and patch.
I’ve also been looking into the Rust test suite failures seen with Alejandro’s v5 series, and I believe I understand what’s happening there.
I’ll follow up separately on that thread with more details and a suggested rework, so the SVH improvements aren’t lost.
For git/git-dbg, this is the HOST_CPU issue I mentioned earlier in the thread. I’ve since confirmed the fix locally and will send the patch shortly.
I’m not currently looking into the Perl, Locale, or NumPy diffs, so those are available for anyone else to pick up.
Thanks,
Sunil Dora
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#245456): https://lists.openembedded.org/g/openembedded-core/message/245456
Mute This Topic: https://lists.openembedded.org/mt/121159956/8968818
Group Owner: openembedded-core+owner@lists.openembedded.org<mailto:openembedded-core+owner@lists.openembedded.org>
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [SunilKumar.Dora@windriver.com<mailto:SunilKumar.Dora@windriver.com>]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 5532 bytes --]
next prev parent reply other threads:[~2026-09-10 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 10:32 Areas we could do with assistance Richard Purdie
2026-09-10 13:25 ` Dora, Sunil Kumar [this message]
2026-09-10 20:13 ` [OE-core] " Richard Purdie
2026-09-10 15:04 ` Ross Burton
2026-09-10 21:06 ` Jaipaul Cheernam
2026-09-10 21:23 ` Richard Purdie
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=2fcf2fd1-9daf-409b-9bd3-8b9168044a1a@windriver.com \
--to=sunilkumar.dora@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 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.