From: akuster808 <akuster808@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core <openembedded-core@openembedded.org>
Subject: Re: M3 build status
Date: Mon, 2 Mar 2020 20:17:58 -0800 [thread overview]
Message-ID: <47102fa1-dd23-b5ce-1fcb-d05d97d74794@gmail.com> (raw)
In-Reply-To: <df13465da1047d41fb47b19c7479a836b8b71245.camel@linuxfoundation.org>
On 3/2/20 8:47 AM, Richard Purdie wrote:
> On Sat, 2020-02-29 at 07:38 -0800, akuster808 wrote:
>> On 2/29/20 5:13 AM, Richard Purdie wrote:
>>> Just to quickly update everyone, a number of patches we probably
>>> wanted
>>> in 3.1 have had issues but have had the issues resolved and the
>>> patches
>>> have now merged. Thanks to all who dived in and helped with those!
>> So no Bind update?
> There is still time, please send an updated patch!
Its unclear to me what change is outstanding.
- armin
>
>>> The patches/issues I'm aware of that are left:
>>>
>>> * ltp upgrade (musl issue)
>>> * util-linux upgrade (breaks wic test, probably simple fix)
>> I can look at the two above but can't start until Sunday so if
>> someone else grabs them today, have at it.
> These are now done thankfully.
>
>>> * coreutils ptest addition (blocked on libmodule-build-per
>>> reproducibility issue)
> Still not done.
>
>>> * psplash systemd race (smurray may have a fix)
> Still not done.
>
>>> * autobuilder new branch handling for initial run test comparisons
>>> (open high bug with RP)
>>> * tinfoil race (open high bug, struggling for owner)
> Both 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 :(
>
>>> * Intermittent selftest failure with SystemExit (High open bug,
>>> Kai owns)
> Still pending.
>
>>> 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
> * gcc buildtools tarball issue
>
> + the bind issue you mention
>
>> So where are patches going doing this time that will be in after the
>> release?
> I try not to encourage people to send upgrade patches during
> stabilisation as its a distraction for everyone and means fewer people
> caring about the release. I have had to queue them in the past since
> people ignore this and I may have to again depending on what people do
> :(.
>
> Cheers,
>
> Richard
>
>
>
>
>
next prev parent reply other threads:[~2020-03-03 4:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 13:13 M3 build status Richard Purdie
2020-02-29 15:38 ` akuster808
2020-03-02 16:47 ` Richard Purdie
2020-03-03 4:17 ` akuster808 [this message]
2020-03-03 7:01 ` Richard Purdie
2020-03-08 8:14 ` Richard Purdie
2020-03-08 13:08 ` Alexander Kanavin
2020-03-08 13:18 ` Richard Purdie
2020-03-08 14:34 ` Richard Purdie
2020-03-08 15:47 ` Trevor Gamblin
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=47102fa1-dd23-b5ce-1fcb-d05d97d74794@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@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 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.