[OE-core] M3 build status

[Richard Purdie]

On Mon, 2020-03-02 at 16:47 +0000, Richard Purdie wrote:
> On Sat, 2020-02-29 at 07:38 -0800, akuster808 wrote:
> 
> > > * coreutils ptest addition (blocked on libmodule-build-per 
> > >   reproducibility issue)
> 
> Still not done.

This is now closer. Alex fixed the libmodule-build-perl and gettext
reproducibility issues (thanks!), I tracked down a glibc issue and
procps one I saw locally. On a fresh autobuilder run we saw:

https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200307-mk0v6ljq/packages/diff-html/
and
https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20200307-5pvgdd3a/packages/diff-html/

which I believe is the remaining blocking issue on coreutils-ptest.

> > > * psplash systemd race (smurray may have a fix)
> 
> Still not done.

Now done.

> > > * LockedSigs intermittent test failure (RP has open high bug, no
> > > clue 
> > >   how to reproduce or why, total mystery)
> 
> Spent hours on this, limited success :(

Turned out to be a logging issue, hopefully fixed.

> 
> > > * Intermittent selftest failure with SystemExit (High open bug,
> > > Kai owns)
> 
> Still pending.

Still pending. There are also other intermittent Medium+ selftest bugs
we're seeing now the source of major failures has been addressed.

> > > As ever, help with any of these welcome. We'll build M3 when a
> > > majority of the above are ready.
> 
> Also, I've realised:
> * there is a high priority pseudo issue assigned to me

Not done.

> * gcc buildtools tarball issue

Moved forwards. The tarball breaks eSDK testing and my fix didn't work.

There is an open question of whether we want to automate use of this or
not and whether we support Centos7 for the LTS with or without the
tarball.

> + the bind issue you mention

We've established we can't take that.

This puts us closer to the M3 build but probably not quite there yet.

Cheers,

Richard