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
Cc: sundeep.kokkonda@windriver.com, Randy.Macleod@windriver.com,
	 alejandro@enedino.org
Subject: Re: [OE-core] [PATCH 0/5] rust: reproducibility fixes for arm build hosts
Date: Mon, 21 Sep 2026 10:46:45 +0100	[thread overview]
Message-ID: <3cd5b736f6fc19ed3242c2da05dd60b675cfe0f1.camel@linuxfoundation.org> (raw)
In-Reply-To: <b8a0599c-a7e4-44b5-b8c9-6a72d14a70fc@linux.microsoft.com>

On Tue, 2026-09-15 at 09:53 -0600, Alejandro Hernandez wrote:
> Hopefully these fix reproducibility issue when built from different
> hosts.
> 
> Unfortunately these go in a bit of a different way than my next
> version, so I will wait for the result before sending to avoid
> confusion, but I'm fine with these if they work, lets just add my
> sign off to the actual patches based off of mine
> instead of the "Patch from Alejandro + OE link".

I just wanted to say a big thanks to you both. The autobuilder is
showing much less delta for the cross build arch tests now, around 30
or so differences in the maximum case. I've added the git fix from
Sunil and some queued some locale and perl fixes I came up with to get
us there but the rust 'noise' is removed, which helps a lot.

Thanks again!

Cheers,

Richard


  parent reply	other threads:[~2026-09-21  9:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 14:18 [PATCH 0/5] rust: reproducibility fixes for arm build hosts sunilkumar.dora
2026-09-15 14:18 ` [PATCH 1/5] rust: drop the cc object-name reproducibility patch sunilkumar.dora
2026-09-15 14:18 ` [PATCH 2/5] rust: hash cc object names relative to their source roots sunilkumar.dora
2026-09-15 14:18 ` [PATCH 3/5] rust: keep the build host triple out of cargo unit metadata sunilkumar.dora
2026-09-15 14:18 ` [PATCH 4/5] rust: backport deterministic DocLinkResMap serialisation sunilkumar.dora
2026-09-15 14:18 ` [PATCH 5/5] rust: sort hygiene data before it is encoded sunilkumar.dora
2026-09-15 15:53 ` [OE-core] [PATCH 0/5] rust: reproducibility fixes for arm build hosts Alejandro Hernandez
2026-09-15 16:10   ` Dora, Sunil Kumar
     [not found]   ` <18D58A6B209991A8.1909126@lists.openembedded.org>
2026-09-15 17:55     ` Dora, Sunil Kumar
2026-09-16  7:11   ` Antonin Godard
2026-09-21  9:46   ` Richard Purdie [this message]
2026-09-21 21:43     ` Alejandro Hernandez

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=3cd5b736f6fc19ed3242c2da05dd60b675cfe0f1.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Randy.Macleod@windriver.com \
    --cc=SunilKumar.Dora@windriver.com \
    --cc=alejandro@enedino.org \
    --cc=alhe@linux.microsoft.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sundeep.kokkonda@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox