All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <steve@sakoman.com>,
	Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] linux-yocto 5.15.48 reproducibility failure
Date: Wed, 03 Aug 2022 23:46:18 +0100	[thread overview]
Message-ID: <830db8ea9f131bf577340c92a36cb5b7870f315f.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAOSpxdZPefjY=513h0vLb-W3dPqkUzBQXh00V6t68M+-9CDogQ@mail.gmail.com>

On Wed, 2022-08-03 at 11:50 -1000, Steve Sakoman wrote:
> On Wed, Jul 6, 2022 at 4:05 AM Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
> > 
> > On Wed, Jul 6, 2022 at 9:31 AM Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > > 
> > > On Wed, 2022-07-06 at 15:29 +0200, Alexandre Belloni wrote:
> > > > Hello Bruce,
> > > > 
> > > > I got the following reproducible build failures:
> > > > 
> > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/1116/steps/12/logs/stdio
> > > > 
> > > > To me, it looks like the in-kernel config changed, did the compression
> > > > alg change?
> > > > 
> > > > Are you able to look at that soon or should I file a bug?
> > > 
> > > FWIW,
> > > http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220705-g8ltxczy/packages/diff-html/
> > > 
> > > and CONFIG_CC_HAS_ASM_GOTO_TIED_OUTPUT=y changed value...
> > 
> > A quick look at the -stable queue to init/Kconfig does indeed show
> > that option arriving .. from my scan of the change, it looks like
> > there are different compilers on the hosts, and hence that check is
> > detecting a buggy gcc (or not) and changing the value.
> > 
> > So one of the build hosts is failing the test, and another isn't.
> > 
> > I'm not sure how to fix that, unless we revert the change. I'll ponder it more.
> 
> Was this issue ever resolved?  I'm seeing it on kirkstone now too :-(

No, it wasn't. I took a quick look and my best guess is that we now
have the kernel wanting to do $CC tests in kConfig and we don't set CC
properly for all our make config calls. I chucked this in master-next
as a quick guess at a possible fix:

https://git.yoctoproject.org/poky/commit/?h=master-next&id=944cc04d1ed316a5652f3d058b966d4cfb9a6b73

but others might know better where we might be missing the CC settings.
I suspect we need to clean up our parameters a bit looking at the
different call site differences.

Cheers,

Richard




  reply	other threads:[~2022-08-03 22:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 13:29 linux-yocto 5.15.48 reproducibility failure Alexandre Belloni
2022-07-06 13:31 ` Richard Purdie
2022-07-06 14:05   ` Bruce Ashfield
2022-08-03 21:50     ` [OE-core] " Steve Sakoman
2022-08-03 22:46       ` Richard Purdie [this message]
2022-08-04  2:33         ` Bruce Ashfield
2022-08-04  6:57           ` Richard Purdie
     [not found]           ` <170812024C9E55A6.12743@lists.openembedded.org>
2022-08-04  7:27             ` Richard Purdie
2022-08-04 13:38               ` Bruce Ashfield
2022-08-05 13:08                 ` Alexandre Belloni
2022-07-06 13:54 ` Bruce Ashfield

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=830db8ea9f131bf577340c92a36cb5b7870f315f.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=steve@sakoman.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.