* Yocto Project Status 30 August 2022 (WW35)
@ 2022-08-30 14:49 sjolley.yp.pm
2022-08-30 15:54 ` [OE-core] " Alexander Kanavin
0 siblings, 1 reply; 6+ messages in thread
From: sjolley.yp.pm @ 2022-08-30 14:49 UTC (permalink / raw)
To: yocto, openembedded-core
[-- Attachment #1: Type: text/plain, Size: 5701 bytes --]
Current Dev Position: YP 4.1 M3 (Feature Freeze)
Next Deadline: 22nd August 2022 YP 4.1 M3 Build
Next Team Meetings:
* Bug Triage meeting Thursday September 1st 7:30 am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Weekly Project Engineering Sync Tuesday August 30th at 8 am PDT (
<https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
<https://zoom.us/j/990892712> )
* Twitch - See <https://www.twitch.tv/theyoctojester>
https://www.twitch.tv/theyoctojester
Key Status/Updates:
* YP 3.1.19 was released
* We are now at feature freeze for 4.1 but M3 has not been built yet.
* We are trying to prepare for the M3 build but the status of too many
issues remains uncertain. In particular:
* llvm buildpaths patch was requested to be rewritten and the rewrite
doesn't work
* rust ppc patch was deemed incorrect
* layer setup changes didn't test successfully
* rust SDK relocation patch is still in progress
* concerns were raised over the rust crossbeam-utils atomics
workaround
* In addition, several other high priority (release blocking) bugs
were identified in bug triage, particularly issues which are occurring
intermittently but regularly and hence causing failed builds. Richard and
Ross own the majority but can't handle all these at once and rather
depressingly, there was nobody to take ownership of some of them. The
current list of open high bugs:
o perl builds hanging indefinitely:
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14902>
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14902
o cve checking crashing intermittently with database issues:
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14899>
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14899
o ptest in gcrypt intermittently but regularly failing on arm:
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14800>
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14800
o build path corruption when llvm is used to build mesa:
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14897>
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14897
o ptest infrastructure issue which stops us debugging an intermittent
failure in lttng: <https://bugzilla.yoctoproject.org/show_bug.cgi?id=14901>
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14901
o intermittent rust SDK host library corruption:
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14892>
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14892
o no automated mechanism to compare releases for ptest regressions:
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14897>
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14897
* Help is very much welcome in trying to resolve our autobuilder
intermittent issues. You can see the list of failures we're continuing to
see by searching for the "AB-INT" tag in bugzilla:
<https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT>
https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
Ways to contribute:
* There are bugs identified as possible for newcomers to the project:
<https://wiki.yoctoproject.org/wiki/Newcomers>
https://wiki.yoctoproject.org/wiki/Newcomers
* There are bugs that are currently unassigned for YP 4.1. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enhan
cements.2FBugs
* We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:
<http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/mai
ntainers.inc>
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.
* Help us resolve CVE issues:
<https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgK
IiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488
&format=interactive> CVE metrics
YP 4.1 Milestone Dates:
* YP 4.1 M3 build date 2022/08/22
* YP 4.1 M3 Release date 2022/09/02
* YP 4.1 M4 build date 2022/10/03
* YP 4.1 M4 Release date 2022/10/28
Upcoming dot releases:
* YP 3.1.19 is released
* YP 4.0.4 build date 2022/09/19
* YP 4.0.4 Release date 2022/09/30
* YP 3.1.20 build date 2022/10/10
* YP 3.1.20 Release date 2022/10/21
* YP 4.0.5 build date 2022/10/31
* YP 4.0.5 Release date 2022/11/11
Tracking Metrics:
* WDD 2469 (last week 2482) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
* Total patches found: 1224 (last week 1212)
* Patches in the Pending State: 329 (27%) [last week 329 (27%)]
* <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
https://autobuilder.yocto.io/pub/non-release/patchmetrics/
The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:
<https://wiki.yoctoproject.org/wiki/TSC>
https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at:
<https://wiki.yoctoproject.org/wiki/Weekly_Status>
https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]
Thanks,
Stephen K. Jolley
Yocto Project Program Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 62459 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [OE-core] Yocto Project Status 30 August 2022 (WW35)
2022-08-30 14:49 Yocto Project Status 30 August 2022 (WW35) sjolley.yp.pm
@ 2022-08-30 15:54 ` Alexander Kanavin
2022-08-30 20:40 ` Richard Purdie
0 siblings, 1 reply; 6+ messages in thread
From: Alexander Kanavin @ 2022-08-30 15:54 UTC (permalink / raw)
To: Stephen Jolley; +Cc: Yocto-mailing-list, OE-core
On Tue, 30 Aug 2022 at 16:49, Stephen Jolley <sjolley.yp.pm@gmail.com> wrote:
> layer setup changes didn’t test successfully
The latest patchset has no known issues.
> o perl builds hanging indefinitely: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14902
I will look into this. Findings will go into the ticket.
Alex
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [OE-core] Yocto Project Status 30 August 2022 (WW35)
2022-08-30 15:54 ` [OE-core] " Alexander Kanavin
@ 2022-08-30 20:40 ` Richard Purdie
2022-08-30 21:14 ` Alexander Kanavin
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Richard Purdie @ 2022-08-30 20:40 UTC (permalink / raw)
To: Alexander Kanavin, Stephen Jolley; +Cc: Yocto-mailing-list, OE-core
On Tue, 2022-08-30 at 17:54 +0200, Alexander Kanavin wrote:
> On Tue, 30 Aug 2022 at 16:49, Stephen Jolley <sjolley.yp.pm@gmail.com> wrote:
> > layer setup changes didn’t test successfully
>
> The latest patchset has no known issues.
I think I may be lagging a little behind on status. I did see a lot of
confusion about the patches and I know they didn't make the last
testing cut. Hopefully they'll be in the next patch.
>
> > o perl builds hanging indefinitely: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14902
>
> I will look into this. Findings will go into the ticket.
Thanks! We haven't quite found the exact trigger to reproduce it but it
seems related to rebuilds somehow.
Cheers,
Richard
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [OE-core] Yocto Project Status 30 August 2022 (WW35)
2022-08-30 20:40 ` Richard Purdie
@ 2022-08-30 21:14 ` Alexander Kanavin
2022-08-31 9:42 ` Alexander Kanavin
2022-08-31 11:16 ` Alexander Kanavin
2 siblings, 0 replies; 6+ messages in thread
From: Alexander Kanavin @ 2022-08-30 21:14 UTC (permalink / raw)
To: Richard Purdie; +Cc: Stephen Jolley, Yocto-mailing-list, OE-core
On Tue, 30 Aug 2022 at 22:40, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> Thanks! We haven't quite found the exact trigger to reproduce it but it
> seems related to rebuilds somehow.
Yes, this usually happens when new patches from master get pulled in
and perl is rebuilding on top of a previous build. It then cleans its
own directory in a way that results in timestamps aligning just so,
that make gets lost in its own rules, and enters an infinite loop.
I've seen this locally several times, and have the 'wrong' tree saved,
but I also don't know how to trigger the arrival at the wrong tree
reliably.
I suspect this patch may be the solution:
https://github.com/arsv/perl-cross/commit/6a47e4fe17aca2ebb4760d8282dbad4422d4e655
Alex
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [OE-core] Yocto Project Status 30 August 2022 (WW35)
2022-08-30 20:40 ` Richard Purdie
2022-08-30 21:14 ` Alexander Kanavin
@ 2022-08-31 9:42 ` Alexander Kanavin
2022-08-31 11:16 ` Alexander Kanavin
2 siblings, 0 replies; 6+ messages in thread
From: Alexander Kanavin @ 2022-08-31 9:42 UTC (permalink / raw)
To: Richard Purdie; +Cc: Stephen Jolley, Yocto-mailing-list, OE-core
On Tue, 30 Aug 2022 at 22:40, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> > > o perl builds hanging indefinitely: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14902
> >
> > I will look into this. Findings will go into the ticket.
>
> Thanks! We haven't quite found the exact trigger to reproduce it but it
> seems related to rebuilds somehow.
The patch is out.
Alex
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [OE-core] Yocto Project Status 30 August 2022 (WW35)
2022-08-30 20:40 ` Richard Purdie
2022-08-30 21:14 ` Alexander Kanavin
2022-08-31 9:42 ` Alexander Kanavin
@ 2022-08-31 11:16 ` Alexander Kanavin
2 siblings, 0 replies; 6+ messages in thread
From: Alexander Kanavin @ 2022-08-31 11:16 UTC (permalink / raw)
To: Richard Purdie; +Cc: Stephen Jolley, Yocto-mailing-list, OE-core
On Tue, 30 Aug 2022 at 22:40, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> I think I may be lagging a little behind on status. I did see a lot of
> confusion about the patches and I know they didn't make the last
> testing cut. Hopefully they'll be in the next patch.
I just resent the complete patchset (across three mailing lists -
this/bitbake/poky). It's a bit tricky for testers working from
poky-contrib, as they need a poky based set, but this is for
individual repos and master-next.
Alex
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-08-31 11:17 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-08-30 14:49 Yocto Project Status 30 August 2022 (WW35) sjolley.yp.pm
2022-08-30 15:54 ` [OE-core] " Alexander Kanavin
2022-08-30 20:40 ` Richard Purdie
2022-08-30 21:14 ` Alexander Kanavin
2022-08-31 9:42 ` Alexander Kanavin
2022-08-31 11:16 ` Alexander Kanavin
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.