Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alejandro Hernandez <alhe@linux.microsoft.com>,
	 SunilKumar.Dora@windriver.com,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3] rust: Avoid passing host-specific information to crates Strict Version Hash
Date: Thu, 27 Aug 2026 08:53:11 +0100	[thread overview]
Message-ID: <e6874bb2ac2d116380c62b2295da246b79136093.camel@linuxfoundation.org> (raw)
In-Reply-To: <18CF75EE37DB8543.642712@lists.openembedded.org>

On Wed, 2026-08-26 at 21:47 +0100, Richard Purdie via lists.openembedded.org wrote:
> On Wed, 2026-08-26 at 14:08 -0600, Alejandro Hernandez wrote:
> > 
> > On 8/26/2026 1:17 PM, Richard Purdie via lists.openembedded.org
> > wrote:
> > > On Wed, 2026-08-26 at 11:25 -0700, Dora, Sunil Kumar via
> > > lists.openembedded.org wrote:
> > > > Hi Alejandro,
> > > > 
> > > > Thanks for chasing this one down. Small notes on v3:
> > > > 
> > > > The commit is tagged [YOCTO #15554], but that bug is
> > > > "reproducibility
> > > > failures with 'rustdoc' on rust 1.75" (path-length dependent),
> > > > RESOLVED FIXED
> > > > since 2024-08-01 via codegen-units=1 / lto=off.
> > > > 
> > > > What you describe here - artifacts differing by build host arch,
> > > > causing
> > > > cross-architecture sstate matches - looks like:
> > > > 
> > > >    [YOCTO #16376] AB-INT: build system architecture
> > > > reproducibility issue
> > > >    https://bugzilla.yoctoproject.org/show_bug.cgi?id=16376
> > > > 
> > > > which is still open. Could you retag it in v4, unless you had a
> > > > reason to
> > > > point at 15554 that I'm missing?
> > > > ---
> > > > One pointer that may or may not be relevant: the 1.97.1 upgrade
> > > > (65271a5d3b)
> > > > carries an LLVM backport:
> > > > 
> > > >    0043-LoopUnroll-Iterate-exit-fold-candidates-in-
> > > > determini.patch
> > > > 
> > > > added for a repro issue seen with rust 1.97.0. I haven't looked
> > > > at whether it
> > > > interacts with the SVH path at all - just flagging it in case
> > > > it's useful context.
> > 
> > Hey Richard,
> > 
> > 
> > Sorry for the incorrect tag.
> 
> No problem, that is at least easily fixed!
> 
> > I'll look into these failures as well and send a v4
> 
> Thanks! I appreciate the work on this as it should improve things a
> lot.
> 
> > > I put v3 in for testing on the autobuilder and it looks promising,
> > > there are some rust test suite failures though:
> > > 
> > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/4472
> > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/66/builds/4577
> > > 
> > > and probably more to follow. We may need to exclude those tests?
> > > 
> > > I also triggered the reproducibility test targets:
> > > 
> > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/121/builds/3
> > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/119/builds/3
> > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/120/builds/3
> > > 
> > > those builds are ongoing.
> 
> One of these completed:
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/120/builds/3
> 
> which leads to:
> 
> https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260826-plagtpam/packages/diff-html/
> 
> There looks to be a locale issue, some python config tweaks, curl-
> config binconfig needing a tweak and a smaller rust issue left. 
> 
> Definitely progress, much fewer recipes showing issues and fewer binary
> ones and more text ones left...

Sadly the other two test runs looked less promising:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/119/builds/3
https://autobuilder.yoctoproject.org/valkyrie/#/builders/121/builds/3

both of which have a lot of rust related looking differences :/

Cheers,

Richard





  parent reply	other threads:[~2026-08-27  7:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 15:54 [PATCH v3] rust: Avoid passing host-specific information to crates Strict Version Hash Alejandro Hernandez
2026-08-26 18:25 ` Dora, Sunil Kumar
2026-08-26 19:17   ` [OE-core] " Richard Purdie
2026-08-26 20:08     ` Alejandro Hernandez
2026-08-26 20:47       ` Richard Purdie
     [not found]       ` <18CF75EE37DB8543.642712@lists.openembedded.org>
2026-08-27  7:53         ` Richard Purdie [this message]
2026-08-28 15:46           ` Alejandro Hernandez
2026-08-28 17:56             ` Richard Purdie
2026-09-03 18:40               ` Dora, Sunil Kumar

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=e6874bb2ac2d116380c62b2295da246b79136093.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=SunilKumar.Dora@windriver.com \
    --cc=alhe@linux.microsoft.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