Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>,
	"openembedded-core" <openembedded-core@lists.openembedded.org>
Subject: Re: AB-INT issues - where we could use help
Date: Tue, 28 Jul 2026 10:10:49 +0200	[thread overview]
Message-ID: <DKA1W17KW1CO.2QZYCZ5V28WA4@bootlin.com> (raw)
In-Reply-To: <8773d1dc4d109da78fa0ffd91bc5667a5f3544d2.camel@linuxfoundation.org>

On Mon Jul 27, 2026 at 11:12 PM CEST, Richard Purdie wrote:
> Hi,
>
> There are at least a couple of intermittent issues where we would
> welcome some help and we now probably have enough information to allow
> debugging/progress.
>
> Firstly, we suspect there is a reproducibility issue arm to x86. This
> is summarised with this reproducibility diff:
>
> https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260726-9wb1l3t4/packages/diff-html/
>
> (from
> https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260726-9wb1l3t4/packages/diff-html/)
>
> I suspect what happened here is that the qemux86-64 files were built
> first on an arm host rather than an x86 host. In general the x86 hosts
> probably beat the arm hosts to it, hence why this is rare.
>
> To test/reproduce this, I'd suggest picking a target machine (say
> qemux86-64) and then building diffutils on both an x86-64 based host
> and on an aarch64 host. Comparing the ptest package will probably
> result in a diff similar to the above, e.g.:
>
> build_triplet·=·aarch64-unknown-linux-gnu
>
> vs.
>
> build_triplet·=·x86_64-pc-linux-gnu
>
> in usr/lib/diffutils/ptest/tests/Makefile amongst other things. I
> suspect picking MACHINE=qemuarm64 would have the same result.
>
> If that reproduces the issue, it would then be a case of iterating
> through the differnces and finding a way to reconcile the output so it
> is the same, independent of build host architecture.
>

Just a follow-up, as I did open a bug entry for this issue:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=16376

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2026-07-28  8:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 21:12 AB-INT issues - where we could use help Richard Purdie
2026-07-28  8:10 ` 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=DKA1W17KW1CO.2QZYCZ5V28WA4@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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