Current Dev Position: YP 3.4 M1

Next Deadline: 7th June 2021 YP 3.4 M1 build

 

Next Team Meetings:

*       Bug Triage meeting Thursday May 20th at 7:30am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*       Monthly Project Meeting Tuesday June 1st at 8am PDT (
<https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
<https://zoom.us/j/990892712> )
*       Weekly Engineering Sync Tuesday May 18th at 8am 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

 

Key Status/Updates:

*       YP 3.2.4 was released
*       YP 3.3.1 is in QA
*       Patch merging to master is continuing and we now have a round of AUH
upgrades to process. We've tried to merge some of the easier ones as there
was autobuilder testing availability. This allows people to concentrate on
the areas where there are issues with the automated upgrade and where we
most need the help.
*       Anuj is unavailable for a few weeks so Richard will be acting as
maintainer for hardknott until he returns (assistance welcome).
*       An open letter about open source project work was sent to various
mailing lists highlighting some of the challenges established project face
from a resourcing perspective:

 
<https://lists.openembedded.org/g/openembedded-architecture/topic/open_sourc
e_maintainers_an/82722442>
https://lists.openembedded.org/g/openembedded-architecture/topic/open_source
_maintainers_an/82722442

*       The multiconfig changes in bitbake continue to cause problems, we
still need simpler test cases to reproduce issues rather than huge builds.
The existing patches seem to fix some workloads and break others. Richard is
trying to fix but trying to fix autobuilder issues and other problems and
these are slow builds to debug.
*       We saw a significant drop in open CVEs reported by the tooling
against master this week (63 down to 18) and hopefully many more of these
have resolutions "in flight". This will allow us to focus on the real issues
and filter out the legacy noise.
*       SMP was enabled for qemu on arm/x86 and we switched x86 to a more
modern cpu/platform
*       One source of the OOM issues on the autobuilder appears to be glibc
usermode testing going out of control and using up all system memory. We are
investigating the best way to mitigate that but it accounts for some of our
intermittent issues.
*       When OOM issues occur an issue was identified in bitbake's heartbeat
events causing bitbake to hang. Ironically this was being heavily used by
the recent autobuilder load debugging code. There is a patch pending to
address this.
*       A rare sstate manifest corruption bug was tracked down thanks to
information from Martin Jansa, a fix has been merged.
*       We have enabled more resource control on the autobuilder for xz
memory/thread usage as that was contributing to the OOM issues. More
investigation is needed into the rpm/deb controls for xz, help there would
be appreciated.
*       Intermittent autobuilder issues continue to occur and are now at a
record high level. 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

We are working to identify the load pattern on the infrastructure that seems
to trigger these.

 

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 3.4. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.4_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.4_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.

 

YP 3.4 Milestone Dates:

*       YP 3.4 M1 build date 2021/06/07
*       YP 3.4 M1 Release date 2021/06/18
*       YP 3.4 M2 build date 2021/07/12
*       YP 3.4 M2 Release date 2021/07/23
*       YP 3.4 M3 build date 2021/08/23
*       YP 3.4 M3 Release date 2021/09/03
*       YP 3.4 M4 build date 2021/10/04
*       YP 3.4 M4 Release date 2021/10/29

 

Planned upcoming dot releases:

*       YP 3.2.4 is in released
*       YP 3.3.1 is in QA
*       YP 3.3.1 release date 2021/05/28
*       YP 3.1.8 build date 2021/05/24
*       YP 3.1.8 release date 2021/06/04
*       YP 3.1.9 build date 2021/06/21
*       YP 3.1.9 release date 2021/07/02
*       YP 3.3.2 build date 2021/07/19
*       YP 3.3.2 release date 2021/07/30
*       YP 3.1.10 build date 2021/07/26
*       YP 3.1.10 release date 2021/08/06
*       YP 3.1.11 build date 2021/09/13
*       YP 3.1.11 release date 2021/9/24

 

Tracking Metrics:

*       WDD 2664 (last week 2674) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
*       OE-Core/Poky Patch Metrics

*       Total patches found: 1297 (last week 1331)
*       Patches in the Pending State: 494 (38%) [last week 497 (37%)]

 

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...@gmail.com
<mailto:sjolley.yp...@gmail.com> 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152034): 
https://lists.openembedded.org/g/openembedded-core/message/152034
Mute This Topic: https://lists.openembedded.org/mt/82913566/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to