2020 Yocto Project Weekly Status Archive

From Yocto Project
Jump to navigationJump to search

Editing Weekly Status (section) Bold textItalic textInternal linkExternal link (remember http:// prefix)Level 2 headlineEmbedded fileFile linkIgnore wiki formattingYour signature with timestampHorizontal line (use sparingly)

Yocto Project Weekly Status Dec. 15, 2020

Current Dev Position: YP 3.3 M2 development
Next Deadline: 18th January 2021 YP 3.3 M2 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.2.1 is due for imminent release
  • YP 3.3 M1 has been through QA and currently under review from the TSC
  • Patches for 3.3 M2 are now being reviewed, tested and merged.
  • The project’s work on reproducibility was mentioned in their monthly newsletter https://reproducible-builds.org/reports/2020-11/
  • CVE statistics continue to look worse for master after ‘improvements’ to the matching code, help in resolving these newly highlighted issues would be much appreciated.
  • Intermittent autobuilder issues continue to occur. 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
  • Given the vacation many people are taking at this time and the expected ramp down in patch load and newsworthy items, we’re not planning another status report until 5th January. The project technical and triage meetings will also ramp down for this period and resume in the first week of January unless there is any pressing development that needs urgent attention.

Ways to contribute:

YP 3.3 Milestone Dates:

  • YP 3.3 M1 is out of QA.
  • YP 3.3 M2 build date 2021/01/18
  • YP 3.3 M2 Release date 2021/01/29
  • YP 3.3 M3 build date 2021/03/01
  • YP 3.3 M3 Release date 2021/03/12
  • YP 3.3 M4 build date 2021/04/05
  • YP 3.3 M4 Release date 2021/04/30

Planned upcoming dot releases:

  • YP 3.2.1 should release soon.
  • YP 3.1.5 build date 2021/01/11
  • YP 3.1.5 release date 2021/01/22
  • YP 3.2.2 build date 2021/02/08
  • YP 3.2.2 release date 2021/02/19
  • YP 3.1.6 build date 2021/02/22
  • YP 3.1.6 release date 2021/03/05
  • YP 3.1.7 build date 2021/03/22
  • YP 3.1.7 release date 2021/04/02

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Dec. 8, 2020

Current Dev Position: YP 3.3 M2 development
Next Deadline: 18th January 2021 YP 3.3 M2 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.2.1 is in QA
  • YP 3.1.4 was released
  • YP 3.3 M1 is due to be built this week once patches currently queued stabilize
  • YP 3.3 development in master is continuing as patches are reviewed, tested and merged with a focus on stabilization for M1.
  • After patches due to merge imminently for M1, reproducible builds have taken a major step forward and we now have a specific exclusions list of packages which don’t build reproducibility. Thanks Alex for the work on this!
  • Python3-pytest and its dependencies have merged to core due to our desire for more automated package testing and the fact it's a dependency for several recipes we need in core. Thanks Tim!
  • CVE statistics have regressed slightly for master as we’ve changed the matching algorithms and more CVEs were ‘identified’ including several many years old and likely not relevant. We’ll work on resolving these over time but the trend continues to be a significant reduction over time.
  • Intermittent autobuilder issues continue to occur. 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

Ways to contribute:

YP 3.3 Milestone Dates:

  • YP 3.3 M1 build date 2020/12/07
  • YP 3.3 M1 Release date 2020/12/18
  • YP 3.3 M2 build date 2021/01/18
  • YP 3.3 M2 Release date 2021/01/29
  • YP 3.3 M3 build date 2021/03/01
  • YP 3.3 M3 Release date 2021/03/12
  • YP 3.3 M4 build date 2021/04/05
  • YP 3.3 M4 Release date 2021/04/30

Planned upcoming dot releases:

  • YP 3.1.4 is released.
  • YP 3.2.1 is in QA.
  • YP 3.2.1 release date 2020/12/4
  • YP 3.1.5 build date 2021/01/11
  • YP 3.1.5 release date 2021/01/22
  • YP 3.2.2 build date 2021/02/08
  • YP 3.2.2 release date 2021/02/19
  • YP 3.1.6 build date 2021/02/22
  • YP 3.1.6 release date 2021/03/05
  • YP 3.1.7 build date 2021/03/22
  • YP 3.1.7 release date 2021/04/02

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Dec. 1, 2020

Current Dev Position: YP 3.3 M1 development
Next Deadline: 7th December 2020 YP 3.3 M1 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.1.4 has been through QA and is now under review for release.
  • YP 3.3 M1 is due to be built next week
  • YP 3.3 development in master is continuing as patches are reviewed, tested and merged.
  • A number of python3 modules have moved to OE-Core, specifically around allowing pytest to operate there as a number of other recipes depend upon it and this seemed the most logical solution.
  • Various improvements have been made to the buildbot UI on the autobuilder and these have now been deployed on our live instance. The helper changes to improve the log separation and make the differences between builds clearer has also merged for master.
  • Intermittent autobuilder issues continue to occur. 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

Ways to contribute:

YP 3.3 Milestone Dates:

  • YP 3.3 M1 build date 2020/12/07
  • YP 3.3 M1 Release date 2020/12/18
  • YP 3.3 M2 build date 2021/01/18
  • YP 3.3 M2 Release date 2021/01/29
  • YP 3.3 M3 build date 2021/03/01
  • YP 3.3 M3 Release date 2021/03/12
  • YP 3.3 M4 build date 2021/04/05
  • YP 3.3 M4 Release date 2021/04/30

Planned upcoming dot releases:

  • YP 3.1.4 is out of QA
  • YP 3.2.1 build date 2020/11/16
  • YP 3.2.1 release date 2020/12/4
  • YP 3.1.5 build date 2021/01/11
  • YP 3.1.5 release date 2021/01/22
  • YP 3.2.2 build date 2021/02/08
  • YP 3.2.2 release date 2021/02/19
  • YP 3.1.6 build date 2021/02/22
  • YP 3.1.6 release date 2021/03/05
  • YP 3.1.7 build date 2021/03/22
  • YP 3.1.7 release date 2021/04/02

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Nov. 24, 2020

Current Dev Position: YP 3.3 M1 development
Next Deadline: 7th December 2020 YP 3.3 M1 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.1.4 will build later this week.
  • YP 3.3 development in master is continuing as patches are reviewed, tested and merged.
  • We plan to backport the sphinx documentation transition back to our LTS after 3.1.4 is built.
  • A small but important issue was identified related to build reproducibility where the host umask was influencing the build output in relatively minor ways. We plan to run a mixture of umasks on the autobuilder infrastructure in future to avoid this source of reproducibility issues. There are patches for the issues queued for master and will be backported in due course.
  • Support for fedora33 has been resolved but required making pseudo-native host specific and not ‘uninative’ due to differences in the way pseudo builds depending on the presence of headers.
  • Hashserve “passthrough” support has merged allowing hashservers to be chained together, thanks Joshua.
  • Intermittent autobuilder issues continue to occur. 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
  • Further autobuilder improvements have been submitted and accepted into upstream buildbot (field history, triggered build summary stats and work name display in build summary). As these are released and deployed, they will make small but important improvements to the autobuilder usability.

Ways to contribute:

YP 3.3 Milestone Dates:

  • YP 3.3 M1 build date 2020/12/07
  • YP 3.3 M1 Release date 2020/12/18
  • YP 3.3 M2 build date 2021/01/18
  • YP 3.3 M2 Release date 2021/01/29
  • YP 3.3 M3 build date 2021/03/01
  • YP 3.3 M3 Release date 2021/03/12
  • YP 3.3 M4 build date 2021/04/05
  • YP 3.3 M4 Release date 2021/04/30

Planned upcoming dot releases:

  • YP 3.1.4 build date 2020/11/2
  • YP 3.1.4 release date 2020/11/13
  • YP 3.2.1 build date 2020/11/16
  • YP 3.2.1 release date 2020/12/4
  • YP 3.1.5 build date 2021/01/11
  • YP 3.1.5 release date 2021/01/22
  • YP 3.2.2 build date 2021/02/08
  • YP 3.2.2 release date 2021/02/19
  • YP 3.1.6 build date 2021/02/22
  • YP 3.1.6 release date 2021/03/05
  • YP 3.1.7 build date 2021/03/22
  • YP 3.1.7 release date 2021/04/02

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Nov. 17, 2020

Current Dev Position: YP 3.3 M1 development
Next Deadline: 7th December 2020 YP 3.3 M1 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.1.4 should build this week now the CVE work has reached a logical point for the build.
  • Master has now opened up for 3.3 development and patches are merging.
  • Dunfell has seen a number of CVE report improvements (count of 202 down to 71 in the past three months), either through patches/upgrades or in corrections to the CVE database information, thanks Steve and all those who’ve helped.
  • The dunfell CVE improvements have also drastically improved the situation with master.
  • Intermittent autobuilder issues continue to occur. 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
  • The SWAT team has been re-established. A new mailing has been created as swat@lists.yoctoproject.org to support this and a number of member organisations have agreed to help staff this team. We are in the process of getting the process running again and in due course there will be the option of other community members being able to help too. The tools and processes are under review to allow us to optimise the process. Thanks to the members and everyone participating to make this happen!
  • There are big improvements underway to the autobuilder display of builds, for example, https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/2744 which shows many more individual steps with more detailed information. *There still needs to be improvements to the configuration markup to make best use of this (help welcome!) but this should significantly improve the autobuilder readability.
  • There are other ideas being discussed around autobuilder usability improvements such as remembering field history (patch submitted to upstream buildbot), better success/failure count reporting and potential replacement of the buildlog wiki page and autobuilder integration with a specific purpose django app.

Ways to contribute:

YP 3.3 Milestone Dates:

  • YP 3.3 M1 build date 2020/12/07
  • YP 3.3 M1 Release date 2020/12/18
  • YP 3.3 M2 build date 2021/01/18
  • YP 3.3 M2 Release date 2021/01/29
  • YP 3.3 M3 build date 2021/03/01
  • YP 3.3 M3 Release date 2021/03/12
  • YP 3.3 M4 build date 2021/04/05
  • YP 3.3 M4 Release date 2021/04/30

Planned upcoming dot releases:

  • YP 3.1.4 build date 2020/11/2
  • YP 3.1.4 release date 2020/11/13
  • YP 3.2.1 build date 2020/11/16
  • YP 3.2.1 release date 2020/12/4
  • YP 3.1.5 build date 2021/01/11
  • YP 3.1.5 release date 2021/01/22
  • YP 3.2.2 build date 2021/02/08
  • YP 3.2.2 release date 2021/02/19
  • YP 3.1.6 build date 2021/02/22
  • YP 3.1.6 release date 2021/03/05
  • YP 3.1.7 build date 2021/03/22
  • YP 3.1.7 release date 2021/04/02

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Nov. 10, 2020

Current Dev Position: YP 3.3 M1 development
Next Deadline: 7th December 2020 YP 3.3 M1 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.2 has been released
  • Master has now opened up for 3.3 development. Unfortunately there have been a lot of issues showing up with some of the more adventurous patches being proposed, the issues are being worked through. Intermittent autobuilder issues continue to occur. 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
  • A YP 3.3 planning document has been created for ideas about what may happen in the YP 3.3 release (assuming there are people to work on the items): https://docs.google.com/document/d/1IHiE0NU0XspDocgxZeLQ_W7o-yr0nVeBjbqImQUtH5A/edit Request edit/suggest access if you want to add to it.
  • YP 3.3 dates for builds, milestones and release have been added below.
  • Anuj Mittal has kindly agreed to maintain the YP 3.2 series (gatesgarth), thanks!
  • The SWAT team has been re-established. A new mailing has been created as swat@lists.yoctoproject.org to support this and a number of member organisations have agreed to help staff this team. We are in the process of getting the process running again and in due course there will be the option of other community members being able to help too. The tools and processes are under review to allow us to optimise the process. Thanks to the members and everyone participating to make this happen!

Ways to contribute:

YP 3.2 Milestone Dates:

  • YP 3.2 M4 released.

YP 3.3 Milestone Dates:

  • YP 3.3 M1 build date 2020/12/07
  • YP 3.3 M1 Release date 2020/12/18
  • YP 3.3 M2 build date 2021/01/18
  • YP 3.3 M2 Release date 2021/01/29
  • YP 3.3 M3 build date 2021/03/01
  • YP 3.3 M3 Release date 2021/03/12
  • YP 3.3 M4 build date 2021/04/05
  • YP 3.3 M4 Release date 2021/04/30

Planned upcoming dot releases:

  • YP 3.1.4 build date 2020/11/2
  • YP 3.1.4 release date 2020/11/13
  • YP 3.2.1 build date 2020/11/16
  • YP 3.2.1 release date 2020/12/4
  • YP 3.1.5 build date 2021/01/11
  • YP 3.1.5 release date 2021/01/22
  • YP 3.2.2 build date 2021/02/08
  • YP 3.2.2 release date 2021/02/19
  • YP 3.1.6 build date 2021/02/22
  • YP 3.1.6 release date 2021/03/05
  • YP 3.1.7 build date 2021/03/22
  • YP 3.1.7 release date 2021/04/02

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Oct. 27, 2020

Current Dev Position: YP 3.3 M1 development
Next Deadline: 7th December 2020 YP 3.3 M1 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.2 rc1 came out of QA but two reported ptest regressions along with a separate issue identified with buildhistory meant we have built an rc2 which is now in QA.
  • It's Yocto Project’s birthday. Happy 10th anniversary everyone and thanks to everyone who has contributed over the last 10 years. It’s the people that make the project what it is!
  • This week is the Embedded Linux Conference Europe which is followed by the Yocto Project Developer Summit. There is still time to register for that: https://events.linuxfoundation.org/yocto-project-summit-europe/
  • Unfortunately, intermittent autobuilder issues continue to occur. 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 Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
  • We have a steadily riding WDD and Medium+ bug count which is a concern.
  • A YP 3.3 planning document has been created for ideas about what may happen in the YP 3.3 release (assuming there are people to work on the items): https://docs.google.com/document/d/1IHiE0NU0XspDocgxZeLQ_W7o-yr0nVeBjbqImQUtH5A/edit Request edit access if you want to add to it.
  • YP 3.3 dates for builds, milestones and release have been added below.

Ways to contribute:

YP 3.2 Milestone Dates:

  • YP 3.2 M4 in QA now.

YP 3.3 Milestone Dates:

  • YP 3.3 M1 build date 2020/12/07
  • YP 3.3 M1 Release date 2020/12/18
  • YP 3.3 M2 build date 2021/01/18
  • YP 3.3 M2 Release date 2021/01/29
  • YP 3.3 M3 build date 2021/03/01
  • YP 3.3 M3 Release date 2021/03/12
  • YP 3.3 M4 build date 2021/04/05
  • YP 3.3 M4 Release date 2021/04/30

Planned upcoming dot releases:

  • YP 3.1.4 build date 2020/11/2
  • YP 3.1.4 release date 2020/11/13
  • YP 3.2.1 build date 2020/11/16
  • YP 3.2.1 release date 2020/12/4
  • YP 3.1.5 build date 2021/01/11
  • YP 3.1.5 release date 2021/01/22
  • YP 3.2.2 build date 2021/02/08
  • YP 3.2.2 release date 2021/02/19
  • YP 3.1.6 build date 2021/02/22
  • YP 3.1.6 release date 2021/03/05
  • YP 3.1.7 build date 2021/03/22
  • YP 3.1.7 release date 2021/04/02

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Oct. 20, 2020

Current Dev Position: YP 3.2 Final Build
Next Deadline: YP 3.2 M4 Feature Freeze - Now

Next Team Meetings:

Key Status/Updates:

  • YP 3.2 rc1 is currently building on the autobuilder.
  • Unfortunately, intermittent autobuilder issues continue to occur, we had a record 8 of them in one full build over the weekend. We’re now holding out hope that better debugging data (such as qemu monitor information) when issues occur will help identify several of the 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 Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
  • We have a steadily riding WDD and Medium+ bug count which is a concern.
  • We realized there was an issue with wiki account creation. These should be created now but please report if there are any issues.
  • A YP 3.3 planning document has been created for ideas about what may happen in the YP 3.3 release (assuming there are people to work on the items): https://docs.google.com/document/d/1IHiE0NU0XspDocgxZeLQ_W7o-yr0nVeBjbqImQUtH5A/edit equest suggest or edit access if you want to add to it.
  • The above document has the proposed dates for YP 3.3 milestones and release.

Ways to contribute:

YP 3.2 Milestone Dates:

  • YP 3.2 M4 building now.
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.4 build date 2020/11/2
  • YP 3.1.4 release date 2020/11/13

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Oct. 13, 2020

Current Dev Position: YP 3.2 M4
Next Deadline: YP 3.2 M4 Feature Freeze - Now

Next Team Meetings:

Key Status/Updates:

  • YP 3.1.3 has been released.
  • We are now (over)due to build M4 rc1. There are currently three high bugs blocking the final M4 build, a buildtools issue where buildtools needs updating in the install script, a toaster issue with recent bitbake cooker process changes and a missing kea init script..
  • Major pseudo changes have been merged and are now testing cleanly on the testing infrastructure. The known community reported issues have also been resolved and a couple of underlying pseudo bugs discovered and fixed too. Interestingly there was around a 2GB reduction in the size of the pseudo databases for core-image-sato after the path filtering was added.
  • Victor did some great work in understanding why qemumips was so much slower than qemumips64 and by changing the number of TLBs (easy in software!). we were able to see a 40% speedup in 32 mips qemu test execution times. A further piece of good news is upstream look willing to add functionality which lets us configure the number of TLBs so we shouldn’t have to maintain anything out of tree, thanks Victor!
  • Unfortunately, intermittent autobuilder issues are still occurring, whilst reducing in frequency and number, possibly due to less frequency full rebuilds. 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 Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.

Ways to contribute:

YP 3.2 Milestone Dates:

  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.3 has released.
  • YP 3.1.4 build date 2020/11/2
  • YP 3.1.4 release date 2020/11/13

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Oct. 6, 2020

Current Dev Position: YP 3.2 M4
Next Deadline: YP 3.2 M4 Feature Freeze - Now

Next Team Meetings:

Key Status/Updates:

  • YP M3 has been released
  • YP 3.1.3 is out of QA, there were questions about a failing ptest but those are due to a test issue, not a regression so its likely to be released imminently.
  • We are now due to build M4 rc1. The builds will happen when the current pseudo issues are resolved to a suitable conclusion for the release.
  • As mentioned above, there is a continued concern about file mode corruption issues in pseudo. We do now have patches which reduce the corruption window by orders of magnitude by they don’t entirely remove the potential race. Test builds have been seeing issues in wic in particular and testing is ongoing to try and identify and fix the remaining issues.
  • Unfortunately, intermittent autobuilder issues are still occurring, whilst reducing in frequency and number, possibly due to less frequency full rebuilds. 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 Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.

Ways to contribute:

YP 3.2 Milestone Dates:

  • YP 3.2 M3 is released.
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.3 is out of QA.
  • YP 3.1.4 build date 2020/11/2
  • YP 3.1.4 release date 2020/11/13

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Sept. 29, 2020

Current Dev Position: YP 3.2 M4
Next Deadline: YP 3.2 M4 Feature Freeze - Now

Next Team Meetings:

Key Status/Updates:

  • YP M3 rc2 has been through QA. We have resolved the beaglebone and bitbake UI issues, the ptest issues remain and need attention in M4. It is likely M3 rc2 will be released.
  • YP 3.1.3 is currently going through QA.
  • Unfortunately intermittent autobuilder issues, whilst reduced, do still remain.
  • Issues with file mode corruption in pseudo have been identified and we’re concerned this may be going undetected in the majority of cases. The issue uncovered would explain several odd bugs we’ve seen over the last few years where file mode bits have disappeared. There are some experimental pseudo patches available that reduce the impact and frequency of these issues but as yet we don’t have a full solution. We’re hampered by a lack of a pseudo maintainer with both the availability and experience to be able to help.
  • We continue to struggle with a number of autobuilder intermittent bugs. 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
  • Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.

Ways to contribute:

YP 3.2 Milestone Dates:

  • YP 3.2 M3 is out of QA and should release soon.
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.3 is built and in QA
  • YP 3.1.4 build date 2020/11/2
  • YP 3.1.4 release date 2020/11/13

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Sept. 22, 2020

Current Dev Position: YP 3.2 M4
Next Deadline: YP 3.2 M4 Feature Freeze - Now

Next Team Meetings:

Key Status/Updates:

  • M3 rc1 has been built and been through QA. Unfortunately beaglebone fails to boot so we’ll have to go to an rc2. There were 4 other issues reported by QA too (3 ptest regressions and a bitbake UI issue).
  • We plan to build 3.1.3 imminently
  • The sphinx documentation transition has merged. There is still work needed to clean up various links and other conversion glitches as well as areas the manual needs to be brought up to date. Any help much appreciated. Big thanks to Nico for driving this!
  • The new documentation can be seen at https://docs.yoctoproject.org/,
  • One significant potential cause for autobuilder timeout issues has been identified, potentially the journal on ext4 filesystems was causing IO prioritisation to fail as the journal only runs with one IO level. We’ve modified the journal options on autobuilder workers to be “writeback” to avoid this. This should reduce autobuilder bitbake timeout issues.
  • Two of the three significant autobuilder issues mentioned last week remain:
    • qemumips fails with systemd with 256MB memory, it needs 512MB. If we enable 512MB, we see random hangs. Unless someone can debug and sort the qemu memory issues, we may end up disabling core-image-sato-sdk and core-image-full-cmdline for qemumips+systemd
    • networking with qemu images appears to glitch at times (particularly slower targets such as ltp and qemumips), the session stalls with “no route to host”. We need better serial interrogation to determine the state of qemu when this happens, it's unclear if qemu/kernel hangs, networking fails or what is breaking. Help to add this extra debugging would be much appreciated.
  • There are new autobuilder issues this week, a pseudo bug appears to be being exposed as well as new intermittent issues, as yet not looked into.
  • We continue to struggle with a number of autobuilder intermittent bugs. 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 Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.

Ways to contribute:

YP 3.2 Milestone Dates:

  • YP 3.2 M3 is out of QA and will be rebuilt
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25
  • YP 3.1.4 build date 2020/11/2
  • YP 3.1.4 release date 2020/11/13

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Sept. 15, 2020

Current Dev Position: YP 3.2 M3
Next Deadline: YP 3.2 M3 Feature Freeze - Now

Next Team Meetings:

Key Status/Updates:

  • M3 has now closed and we’re at feature freeze for 3.2.
  • We continue to be in holding pattern for M3 whilst we sort out the sphinx documentation migration. We’re at a point where we just need to press on and complete it.
  • There are three significant autobuilder issues being faced currently:
    • qemumips fails with systemd with 256MB memory, it needs 512MB. If we enable 512MB, we see random hangs. Unless someone can debug and sort the qemu memory issues, we may end up disabling core-image-sato-sdk and core-image-full-cmdline for qemumips+systemd
    • networking with qemu images appears to glitch at times (particularly slower targets such as ltp and qemumips), the session stalls with “no route to host”. We need better serial interrogation to determine the state of qemu when this happens, its unclear if qemu/kernel hangs, networking fails or what is breaking.
    • The timeouts in bitbake have been narrowed down to the “SyncThread” which writes out the cache data to disk stalling for around 90s. We don’t have a plan to address this right now but its at least process in identifying the cause
  • The bitbake parsing hangs should hopefully all be resolved now, thanks to Joshua for help there.
  • A preview of the sphinx built documentation is available at https://docs.yoctoproject.org/, work is ongoing to complete the migration work and blocking M3.
  • We continue to struggle with a number of autobuilder intermittent bugs. 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 Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
  • One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs

YP 3.2 Milestone Dates:

  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Sept. 8, 2020

Current Dev Position: YP 3.2 M3
Next Deadline: YP 3.2 M3 Feature Freeze - Now

Next Team Meetings:

Key Status/Updates:

  • M3 has now closed and we’re at feature freeze for 3.2.
  • We now have most patches merged for 3.2, the main remaining question is around the documentation. The current plan is to merge the sphinx branches into master and then build M3.
  • There is a new technique being used to try and mitigate some of the runtime autobuilder issues, so far the results from that have looked promising (using the runqemu-renice script).
  • Some fixes for bitbake’s parsing handling have merged which hopefully will address some of the hung process issues we’ve been seeing. Some of the issues look like potential issues in upstream python multiprocessing.
  • There have also been significant cleanups to the server process logging and reporting of processes holding the bitbake lock.
  • The work in enabling PRServ to work well with hash equivalence has merged.
  • A preview of the sphinx built documentation is now available at https://docs.yoctoproject.org/, work is ongoing to complete the migration work.
  • We continue to struggle with a number of autobuilder intermittent bugs. 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 Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
  • One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • For older releases, we’ve been struggling to handle these with the changing distros on the autobuilder infrastructure. We’ve managed to pull together various pieces of work to allow these older releases to be built on the infrastructure and an email discussing this was sent to the openembedded-architecture list. It will mean adding some larger series of patches to the older release branches for the yocto-autobuilder-helper and openembedded-core repositories but it is believed this is in the best interests of being able to test these older releases going forward if needed. This may also reduce the barrier to entry for new maintainers and community maintenance.

YP 3.2 Milestone Dates:

  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Sept. 8, 2020

Current Dev Position: YP 3.2 M3
Next Deadline: YP 3.2 M3 Feature Freeze - Now

Next Team Meetings:

Key Status/Updates:

  • M3 has now closed and we’re at feature freeze for 3.2.
  • We now have most patches merged for 3.2, the main remaining question is around the documentation. The current plan is to merge the sphinx branches into master and then build M3.
  • There is a new technique being used to try and mitigate some of the runtime autobuilder issues, so far the results from that have looked promising (using the runqemu-renice script).
  • Some fixes for bitbake’s parsing handling have merged which hopefully will address some of the hung process issues we’ve been seeing. Some of the issues look like potential issues in upstream python multiprocessing.
  • There have also been significant cleanups to the server process logging and reporting of processes holding the bitbake lock.
  • The work in enabling PRServ to work well with hash equivalence has merged.
  • A preview of the sphinx built documentation is now available at https://docs.yoctoproject.org/, work is ongoing to complete the migration work.
  • We continue to struggle with a number of autobuilder intermittent bugs. 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 Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
  • One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • For older releases, we’ve been struggling to handle these with the changing distros on the autobuilder infrastructure. We’ve managed to pull together various pieces of work to allow these older releases to be built on the infrastructure and an email discussing this was sent to the openembedded-architecture list. It will mean adding some larger series of patches to the older release branches for the yocto-autobuilder-helper and openembedded-core repositories but it is believed this is in the best interests of being able to test these older releases going forward if needed. This may also reduce the barrier to entry for new maintainers and community maintenance.

YP 3.2 Milestone Dates:

  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Sept. 1, 2020

Current Dev Position: YP 3.2 M3
Next Deadline: YP 3.2 M3 Feature Freeze - Now

Next Team Meetings:

Key Status/Updates:

  • M3 has now closed and we’re at feature freeze for 3.2.
  • There are a number of patches we need for 3.2 which are still being sorted out and M3 will build once that has happened.
  • Bitbake server startup has been changed to avoid the issues previously discovered. There are some issues with traceback handling/reporting during early init which are being resolved as a result of that and those have open bugs.
  • The server changes have improved memory resident bitbake but some issues with state tracking still remain so memory resident bitbake will not be the default until 3.3, assuming we can debug those remaining problems by early in 3.3.
  • There has been work in enabling PRServ to work well with hash equivalence, thanks to Mark for sorting out this long standing work item. We aim to have this in 3.2 but some tests need fixing before it can completely merge.
  • We will process one last round of recipe upgrades before we build M3.
  • We were finally able to change the fcommon gcc defaults back to standard, thanks to all who helped make that happen.
  • The number of autobuilder intermittent bugs has continued to rise unfortunately. 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
  • Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
  • One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • Globbing support in file:// urls has been removed.

YP 3.2 Milestone Dates:

  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Aug. 25, 2020

Current Dev Position: YP 3.2 M3
Next Deadline: YP 3.2 M3 build date 2020/8/31 - FEATURE FREEZE

Next Team Meetings:

Key Status/Updates:

  • YP 3.0.4 was released
  • M3 is due to close at the end of the week and this is the feature freeze point for 3.2
  • After much debugging, we’ve concluded the bitbake cooker/server launch process is terminally flawed, you can’t fork a python process into two independent python processes and have the internal python state machinery work correctly. *As such, we’re going to have to make some major changes to the way the bitbake cooker/server startup happens.
  • On a positive note, those server changes have forced many of the memory resident bitbake bugs to the surface and the new code appears to fix them, bringing memres bitbake much closer to being usable, maybe even becoming a default in this release if testing goes well.
  • There is concern about invasive changes like this with regard to LTS/dunfell where these bitbake bugs are also present. Ultimately we will make a decision about backporting based upon patch stability and user feedback from the LTS users.
  • We may delay M3 slightly to enable the bitbake server changes to merge since these are important for release and work making/merging.
  • The number of autobuilder intermittent bugs has continued to rise unfortunately. 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 Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
  • One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • There is a proposal on the bitbake list to remove globbing support from file:// urls. Usage of these urls currently breaks source file checksumming which users don’t realise, it can’t be fixed in a sane way so and the most common use cases has easy alternatives such as referencing a directory as a file:// url without globs so removing globbing support appears to be the best way forward.
  • We have switched to the 5.8 kernel by default, it's taken a while to get through all the different issues but we appear to be there now, thanks to Bruce for working through many of them!
  • Some long standing musl SDK issues should be resolved now.


YP 3.2 Milestone Dates:

  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.4 was released
  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Aug. 18, 2020

Current Dev Position: YP 3.2 M3
Next Deadline: YP 3.2 M3 build date 2020/8/31

Next Team Meetings:

Key Status/Updates:

  • YP 3.0.4 is going through QA at this time
  • YP 3.2 M2 was released
  • We’ve had a sharp increase in the autobuilder intermittent bugs
  • 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 Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
  • One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • Help with any of the recent failed AUH recipe upgrades would also be appreciated. We’d also like to remind recipe maintainers to submit the successful upgrades.
  • We are trying to drop the fcommon/fno-common hacks from gcc however there are still a number of failures it triggers, particularly in perf. Khem has done great work in fixing many of the issues already.
  • Improved shell backtracing capability was added to bitbake, thanks Chris.

YP 3.2 Milestone Dates:

  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.4 is in QA
  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Aug. 11, 2020

Current Dev Position: YP 3.2 M3
Next Deadline: YP 3.2 M3 build date 2020/8/31

Next Team Meetings:

Key Status/Updates:

  • YP 3.2 M2 is out of QA and going through release approval
  • We’re now in M3 which is the last milestone for new feature development for this release
  • YP 3.0.4 is due to be built this week and will be the last point release for zeus as we migrate over to our new LTS policy and cadence.
  • A number of new intermittent autobuilder failures were seen this week and logged in bugzilla including one showing signs of another bitbake lockfile race issue.
  • You can see the rest of 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 Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
  • One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • Help with any of the recent failed AUH recipe upgrades would also be appreciated.

YP 3.2 Milestone Dates:

  • YP 3.2 M2 should release soon.
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status Aug. 4, 2020

Current Dev Position: YP 3.2 M3
Next Deadline: YP 3.2 M3 build date 2020/8/31

Next Team Meetings:

Key Status/Updates:

YP 3.2 Milestone Dates:

  • YP 3.2 M2 build is in QA
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 is released
  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status July 28, 2020

Current Dev Position: YP 3.2 M2
Next Deadline: YP 3.2 M2 build date 2020/7/27

Next Team Meetings:

Key Status/Updates:

  • This week a build race in perl was tracked down, the other issue of concern are the qemumips systemd (poky-altcfg) image testing failures (reasons unknown). 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 Help with any of these would be much appreciated.
  • YP 3.1.2 has been built and is in QA. An issue with toaster and recent bitake changes may potentially impact the release.
  • YP 3.2 M2 will be built this week to follow YP 3.1.2 in QA.
  • One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • Help with any of the recent failed AUH recipe upgrades would also be appreciated.

YP 3.2 Milestone Dates:

  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 is in QA
  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status July 21, 2020

Current Dev Position: YP 3.2 M2
Next Deadline: YP 3.2 M2 build date 2020/7/27

Next Team Meetings:

Key Status/Updates:

  • The number of intermittent race issues is reduced however we are still seeing some recurring issues and some new issues too. 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
  • Help with any of these would be much appreciated.
  • We are planning to do a build of 3.1.2 this week as the project appears to be in reasonable shape after the recent race fixes that were backported.
  • We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
  • Another way to help the project is to help us with bugs that are currently unassigned but ideally needed during 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • Help with any of the recent failed AUH recipe upgrades would also be appreciated.

YP 3.2 Milestone Dates:

  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/7/20
  • YP 3.1.2 release date 2020/7/31
  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status July 14, 2020

Current Dev Position: YP 3.2 M2
Next Deadline: YP 3.2 M2 build date 2020/7/27

Next Team Meetings:

Key Status/Updates:

  • A key autobuilder race has been identified as a race around the bitbake lock file which will hopefully continue to reduce the number of intermittent failures being seen. It potentially explains a number of the open bugs. 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
  • We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
  • Another way to help the project is to help us with bugs that are currently unassigned but ideally needed during 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • We’re planning to migrate the project documentation from docbook to sphinx. If you’re interested/able to help with this please join the discussion over on the docs mailing list.

YP 3.2 Milestone Dates:

  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status July 7, 2020

Current Dev Position: YP 3.2 M2
Next Deadline: YP 3.2 M2 build date 2020/7/27

Next Team Meetings:

Key Status/Updates:

  • Thanks to everyone who attended, helped out, organised or otherwise contributed to our ELC presence and YP Dev Day last week, we believe it was successful and people found it interesting and useful.
  • We continue to be concerned about autobuilder stability, we’re continuing to see high numbers of intermittent failures. You can see the list of failures we’re seeing by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
  • Help is urgently needed to bring these to a manageable level. We have managed to resolve or work around some of these issues over the past week and are starting to see green builds again.
  • We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
  • Another way to help the project is to help us with bugs that are currently unassigned but ideally needed during 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • We’re pleased to announce we have a new manual in the Yocto Project documentation ‘bookshelf’ which covers the project’s testing processes and infrastructure including the autobuilder and resulttool. A work-in-progress version of this can be viewed here: https://www.yoctoproject.org/docs/docs_temp/test-manual/test-manual.html. So far, it contains basic information in key areas, we’re happy to take feedback on areas that are missing or need more information and/or take contributions to further extend this work.

YP 3.2 Milestone Dates:

  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status June 30, 2020

Current Dev Position: YP 3.2 M2
Next Deadline: YP 3.2 M2 build date 2020/7/27

Next Team Meetings:

Key Status/Updates:

  • YP 3.2 M1 was released.
  • We’ve updated to a new version of the buildtools tarball for master and dunfell
  • We continue to be concerned about autobuilder stability, we’re continuing to see high numbers of intermittent failures. You can see the list of failures we’re seeing by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT Help is urgently needed to bring these to a manageable level.
  • We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
  • If anyone has thoughts on attracting and recognising project contributors and contributions, we would be interested in ideas and assistance in that area.
  • It is ELC this week, please stop by the booth and/or ELC #2-track-yocto-project slack channel and say hi. There are still places available on our virtual Developer Day: https://events.linuxfoundation.org/yocto-dev-day-north-america/
  • Another way to help the project is to help us with bugs that are currently unassigned but ideally needed during 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • We’re pleased to announce we have a new manual in the Yocto Project documentation ‘bookshelf’ which covers the project’s testing processes and infrastructure including the autobuilder and resulttool. A work-in-progress version of this can be viewed here: https://www.yoctoproject.org/docs/docs_temp/test-manual/test-manual.html. So far, it contains basic information in key areas, we’re happy to take feedback on areas that are missing or need more information and/or take contributions to further extend this work.

YP 3.2 Milestone Dates:

  • YP 3.2 M1 is released.
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status June 23, 2020

Current Dev Position: YP 3.2 M2
Next Deadline: YP 3.2 M2 build date 2020/7/27

Next Team Meetings:

Key Status/Updates:

  • YP 3.1.1 was released
  • YP 3.2 M1 is through QA and awaiting a release decision. The only defects found were two valgrind ptest results so it's likely to release.
  • We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
  • We continue to be concerned about autobuilder stability, we’re continuing to see high numbers of intermittent failures (along with instability in upstream repositories which is now also breaking builds). A list of issues was posted to the OE-Core mailing list, there are other older bugs which have also recurred. We have figured out some fixes but help is urgently needed to bring these to a manageable level.
  • If anyone has thoughts on attracting and recognising project contributors and contributions, we would be interested in ideas and assistance in that area.
  • There remain a large number of bugs that we’d ideally like to fix in 3.2 M2 but they are “unassigned”, there is nobody to work on them. If anyone has time, looking at these bugs would be a great way to help us. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • We’re pleased to announce we have a new manual in the Yocto Project documentation ‘bookshelf’ which covers the project’s testing processes and infrastructure including the autobuilder and resulttool. A work-in-progress version of this can be viewed here: https://www.yoctoproject.org/docs/docs_temp/test-manual/test-manual.html. So far, it contains basic information in key areas, we’re happy to take feedback on areas that are missing or need more information and/or take contributions to further extend this work.
  • Next week is ELC which is taking place virtually this year and Yocto Project has a presence there. There is also a virtual Yocto Project Developer Day: https://events.linuxfoundation.org/yocto-dev-day-north-america/
  • On a positive note, we are looking the closest we’ve ever been to upstream software versions thanks to AUH and work from Alex in particular, the recent AUH reports have been shorter than ever with low numbers of upgrade failures.

YP 3.2 Milestone Dates:

  • YP 3.2 M1 should be released shortly.
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.1 was released
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status June 16, 2020

Current Dev Position: YP 3.2 M1
Next Deadline: YP 3.2 M1 build date 2020/6/16

Next Team Meetings:

Key Status/Updates:

  • YP 3.1.1 is out from QA and had no defects raised so is likely to be released after review
  • YP 3.2 M1 will be built as soon as we have a clean build run of the currently queued patches. We’ve not seen anything else pending critical to M1.
  • We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
  • There was a key fix to the gitsm fetcher which resolved autobuilder regressions, thanks Paul Barker for helping resolve that at short notice.
  • There were some important improvements to multiconfig this week so that multiconfig task hashes are correctly accounted for and rebuilt as well as BBMASK being handled correctly in individual multiconfigs, thanks Joshua Watt for those improvements.
  • The biggest concern for both LTS and master right now are the intermittent test failures that keep occurring on the infrastructure, we’re struggling to get clean builds of either branch due to these issues. Instability in the upstream distros we run on (which we regularly pull for security updates) are sadly contributing to the issues, seemingly more significantly than usual.
  • If anyone has thoughts on attracting and recognising project contributors and contributions, we would be interested in ideas and assistance in that area.
  • There remain a large number of bugs that we’d ideally like to fix in 3.2 M2 but they are “unassigned”, there is nobody to work on them. If anyone has time, looking at these bugs would be a great way to help us. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.1.1 should be released shortly.
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status June 9, 2020

Current Dev Position: YP 3.2 M1
Next Deadline: YP 3.2 M1 build date 2020/6/16

Next Team Meetings:

Key Status/Updates:

  • YP 2.7.4 was released
  • YP 3.1.1 has been built with two issues being investigated before it enters QA
  • A significant number of upgrades have merged into master and we are up to date with a majority of recipes, particularly due work from Alex, thanks! One which isn’t and is looking slightly more problematic is the qemu upgrade to 5.0.0, help would be welcome there.
  • YP 3.2 M1 is due to build next week so patches for M1 need to be sent for review now in order to make it in.
  • We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
  • There remain a large number of bugs that we’d ideally like to fix in 3.2 M1 (or M2) but they are “unassigned”, there is nobody to work on them. If anyone has time, looking at these bugs would be a great way to help us. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 2.7.4 has been released
  • YP 3.1.1 build date 2020/6/09
  • YP 3.1.1 release date 2020/6/20
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status June 2, 2020

Current Dev Position: YP 3.2 M1
Next Deadline: YP 3.2 M1 build date 2020/6/16

Next Team Meetings:

Key Status/Updates:

  • YP 3.0.3 has been released
  • YP 2.7.4 is awaiting final approval and likely to be released today
  • We’re hoping to build 3.1.1 later this week when the current round of patches in review merge
  • The autobuilder is now running Fedora 32 and Ubuntu 20.04 workers, thanks Michael
  • There are a large number of updates nearly ready for merge in master-next which brings many of our versions up to date, thanks Alex!
  • There remain a large number of bugs that we’d ideally like to fix in 3.2 M1 (or M2) but they are “unassigned”, there is nobody to work on them. If anyone has time, looking at these bugs would be a great way to help us. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.3 has been released
  • YP 2.7.4 is out of QA
  • YP 2.7.4 release will be today
  • YP 3.1.1 build date 2020/6/09
  • YP 3.1.1 release date 2020/6/20
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status May 26, 2020

Current Dev Position: YP 3.2 M1
Next Deadline: YP 3.2 M1 build date 2020/6/16

Next Team Meetings:

Key Status/Updates:

  • YP 3.0.3 is in QA result review, there were ptest regressions but these look intermittent in nature and hence unlikely to block release
  • YP 2.7.4 should be built this week
  • One of the autobuilder issues where workers were hanging was tracked down to a NFS incompatibility between the NAS and new kernel versions. The NAS was upgraded to resolve this at a cost of some short notice downtime.
  • There remain a large number of bugs that we’d ideally like to fix in 3.2 M1 (or M2) but they are “unassigned”, there is nobody to work on them. If anyone has time, looking at these bugs would be a great way to help us. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
  • There continue to be other intermittent autobuilder issues in both master and dunfell which we’re trying to track down. These ones look related to the code rather than infrastructure.
  • The AUH is now implemented as an autobuilder job and will be run from there in future.

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.3 is out of QA and the results are being reviewed.
  • YP 3.0.3 release date 2020/5/15
  • YP 2.7.4 build date 2020/5/18
  • YP 2.7.4 release date 2020/5/29
  • YP 3.1.1 build date 2020/6/29
  • YP 3.1.1 release date 2020/7/10
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status May 19, 2020

Current Dev Position: YP 3.2 M1
Next Deadline: YP 3.2 M1 build date 2020/6/16

Next Team Meetings:

Key Status/Updates:

  • YP 3.0.3 is in QA and due out on 21st May
  • Gcc 10 merged to master, with the ‘no-common’ default change disabled for now whilst we address the other gcc 10 issues first, then we’ll loop back to that.
  • We are struggling with autobuilder infrastructure problems, in particular with NFS locking but also with cancelled builds not terminating correctly. These are having a significant negative impact on master and all stable builds and are a significant concern as there is no clear path forward to any resolution.
  • Patches continue to merge into master but at a slower rate than normal. The patch submission rate has dropped slightly which has helped ensure there isn’t a huge backlog.
  • We’re moving the AUH job functionality to the autobuilder and integrating it there which should mean it's easier to reproduce its functionality and allows more people to see what it's doing and work on/with it. This should also reduce hosting costs.

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.3 is in QA
  • YP 3.0.3 release date 2020/5/15
  • YP 2.7.4 build date 2020/5/18
  • YP 2.7.4 release date 2020/5/29
  • YP 3.1.1 build date 2020/6/29
  • YP 3.1.1 release date 2020/7/10
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status May 12, 2020

Current Dev Position: YP 3.2 M1
Next Deadline: YP 3.2 M1 build date 2020/6/16

Next Team Meetings:

Key Status/Updates:

  • Patches continue to merge into master, there have been a number of infrastructure issues and build failures which have delayed some patches until we could get clean builds
  • We’re nearly ready to merge gcc 10 to master with some mingw issues being the currently known remaining blocker.
  • A number of other slightly more invasive changes are merging such as the changing of QA warnings to become errors and changes to the way libva is built. Some further, more invasive changes are in the queue (e.g. image sstate structure) so review of the patch queue by people with interests in these things is appreciated.
  • We believe autoconf may release a new version soon (the first in a few years) so have worked with autoconf upstream to ensure it should work for us, reporting test results back.
  • YP 3.0.3 will build this week.

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.3 build date 2020/5/4
  • YP 3.0.3 release date 2020/5/15
  • YP 2.7.4 build date 2020/5/18
  • YP 2.7.4 release date 2020/5/29
  • YP 3.1.1 build date 2020/6/29
  • YP 3.1.1 release date 2020/7/10
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status May 5, 2020

Current Dev Position: YP 3.2 M1
Next Deadline: YP 3.2 M1 build date 2020/6/16

Next Team Meetings:

Key Status/Updates:

  • We are now merging patches into master, debugging some of the issues has proven problematic but we’re making good progress on various deferred upgrades.
  • In particular there was a further problem with buildtools-extended-tarball which ended up ‘corrupting’ sstate by over-optimising binaries so they wouldn't run on older CPUs. Fixes for this have merged and we’ll need to release a new buildtools tarball.
  • The 3.1 stable branch has started taking its first rounds of patches, help with review of these would be much appreciated.
  • A 3.0 stable build is due as soon as the current patches in review are sorted out.
  • The multilib issue mentioned in previous status reports and on the architecture list is proving tricky, do we make the invasive changes in master-next for master now they appear to work? Backport to dunfell? Or try and come up with a more invasive core bitbake change?
  • We are aware of some issues with bug trend metrics due to server transitions and are working to resolve those.

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.3 build date 2020/5/4
  • YP 3.0.3 release date 2020/5/15
  • YP 2.7.4 build date 2020/5/18
  • YP 2.7.4 release date 2020/5/29
  • YP 3.1.1 build date 2020/6/29
  • YP 3.1.1 release date 2020/7/10
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status April 28, 2020

Current Dev Position: YP 3.2 M1
Next Deadline: YP 3.2 M1 build date 2020/6/16

Next Team Meetings:

Key Status/Updates:

  • YP 3.1 was released, thanks to everyone who contributed!
  • The stable maintainer for the 3.1 LTS release is Steve Sakoman
  • YP 3.1 (dunfell) has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • Patches have started merging again into master. We’ve already had some challenging issues to debug with them on the autobuilder where the root cause turned out to be an underlying QA test code issue exposed by test ordering issues.
  • Master branch development will open up later this week, there are already some patches queued and tested in master-next
  • The multilib discussion on the openembedded-architecture list has continued with the potential of new bitbake support to better enable class extensions (which enable native and nativesdk variants as well as multilib).
  • We’ve identified some issues with the new buildtools-extended-tarball so we’ll be making a new version of that and porting fixes to the stable branch.
  • We are aware of some issues with bug trend metrics this week due to server transitions and are working to resolve those.

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.3 build date 2020/5/4
  • YP 3.0.3 release date 2020/5/15
  • YP 2.7.4 build date 2020/5/18
  • YP 2.7.4 release date 2020/5/29
  • YP 3.1.1 build date 2020/6/29
  • YP 3.1.1 release date 2020/7/10
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status April 21, 2020

Current Dev Position: YP 3.1 Being released
Next Deadline: YP 3.1 release date 2020/4/24

Next Team Meetings:

Key Status/Updates:

  • YP 3.1 will be released imminently
  • We’re pleased to be able to announce that the stable maintainer for the 3.1 LTS release will be Steve Sakoman
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • The 3.2 planning document where we’ve been discussing potential 3.2 developments is available at: https://docs.google.com/document/d/100bTV-etO0joh6rAkcr7smlZ9iuENG_8BtaXs_vb54c/edit?usp=sharing
  • Master branch development will open up later this week, there are already some patches queued and tested in master-next
  • There is discussion on the openembedded-architecture list about a particularly troublesome multilib issue which doesn’t appear to have any good resolution at present.
  • We are aware of some issues with bug trend metrics this week due to server transitions and are working to resolve those.

YP 3.1 Dates

  • YP 3.1 M4 In review for release
  • YP 3.1 M4 Release date 2020/4/24

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.3 build date 2020/5/4
  • YP 3.0.3 release date 2020/5/15
  • YP 2.7.4 build date 2020/5/18
  • YP 2.7.4 release date 2020/5/29
  • YP 3.1.1 build date 2020/6/29
  • YP 3.1.1 release date 2020/7/10
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status April 14, 2020

Current Dev Position: YP 3.1 Review for release
Next Deadline: YP 3.1 release date 2020/4/24

Next Team Meetings:

Key Status/Updates:

  • 3.1 rc2 has been through QA and is now being reviewed for release
  • 3.1 rc1 was abandoned prior to QA due to concerns about some recent changes
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • We’re continue to work on bug fixing since if we do need to rebuild, those fixes can be potentially included
  • We are now considering planning for 3.2, there is a planning document at https://docs.google.com/document/d/100bTV-etO0joh6rAkcr7smlZ9iuENG_8BtaXs_vb54c/edit?usp=sharing
  • The planning process for 3.2 is likely to be more lightweight than in the past as the project simply doesn’t have the engineering resources that used to be available for new feature work at this time. We will continue to work on the items left over from previous releases in priority order, as well as trying to reduce the number of open bugs.

YP 3.1 Dates

  • YP 3.1 M4 In review for release
  • YP 3.1 M4 Release date 2020/4/24

YP 3.2 Milestone Dates:

  • YP 3.2 M1 build date 2020/6/16
  • YP 3.2 M1 Release date 2020/6/26
  • YP 3.2 M2 build date 2020/7/27
  • YP 3.2 M2 Release date 2020/8/7
  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

Planned upcoming dot releases:

  • YP 3.0.3 build date 2020/5/4
  • YP 3.0.3 release date 2020/5/15
  • YP 2.7.4 build date 2020/5/18
  • YP 2.7.4 release date 2020/5/29
  • YP 3.1.1 build date 2020/6/29
  • YP 3.1.1 release date 2020/7/10
  • YP 3.0.4 build date 2020/8/10
  • YP 3.0.4 release date 2020/8/21
  • YP 3.1.2 build date 2020/9/14
  • YP 3.1.2 release date 2020/9/25

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status April 7, 2020

Current Dev Position: YP 3.1 M4 - RC built and in QA
Next Deadline: YP 3.1 release date 4/24/2020

Next Team Meetings:

Key Status/Updates:

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M4 built and is in QA
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 3.0.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status March 31, 2020

Current Dev Position: YP 3.1 M4 - Stabilization- Final RC builds
Next Deadline: YP 3.1 M4 build date 3/30/2020

Next Team Meetings:

Key Status/Updates:

  • 3.1 M3 was released
  • The 3.1 rc1 build has not happened yet, the final remaining patches are being worked upon and will be built when the remaining high issues are resolved.
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • The focus is now on stabilizing and bug fixing for the final release
  • We continue to have concerns about the number of autobuilder intermittent failures, particularly with this being an LTS release however the remaining issues are proving hard to reproduce and track down.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 3.0.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status March 24, 2020

Current Dev Position: YP 3.1 M4 - Stabilization
Next Deadline: YP 3.1 M4 build date 3/30/2020

Next Team Meetings:

Key Status/Updates:

  • M3 is through QA and due to be released.
  • The first M4 rc candidate is due to be built on Monday.
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • We’ve uncovered significant issues with the datastore connector approach in tinfoil. There is a proposed fix which effectively rewrites it which is not something undertaken lightly at this point in release but reluctantly, is probably necessary.
  • The focus is now on stabilizing and bug fixing for the final release

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M3 being reviewed for release
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 3.0.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status March 17, 2020

Current Dev Position: YP 3.1 M4 - Stabilization
Next Deadline: YP 3.1 M4 build date 3/30/2020

Next Team Meetings:

Key Status/Updates:

  • M3 has now been built and is in QA. We are therefore feature frozen.
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • There were logging changes merged to better handle hashequiv and usability concerns, thanks Joshua
  • We have seen a welcome rise in green builds recently although several key intermittent failures have not been addressed. It is crucial for an LTS release we do resolve these.
  • Recipe upgrades are now unlikely to be merged into 3.1 as we focus on stabilizing and bug fixing for the final release

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M3 is in QA
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 3.0.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status March 10, 2020

Current Dev Position: YP 3.1 M3 - At Feature Freeze, build pending
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

Key Status/Updates:

  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • We are now past M3 feature freeze. The blocking issues continue to reduce, thanks to everyone who has contributed fixes. The remaining issues are:
    • continued minor bugs with buildtools tarball integration
    • coreutils ptest blocked on reproducibility issues with gcc-plugins
    • SystemExit() intermittent selftest failure
    • pseudo sysroot high priority bug
  • There are significant changes proposed to bitbake’s logging structure to address concerns raised by hashequiv changes. These are currently in testing and are likely to become part of M3 given the timing, wider review is welcome.
  • Recipe upgrades are now unlikely to be merged into 3.1 as we focus on stabilizing and bug fixing for the release
  • Autobuilder build results continue to be a concern as we’re not getting green builds very often due to multiple varied issues.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 3.0.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status March 3, 2020

Current Dev Position: YP 3.1 M3 - At Feature Freeze, build pending
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

Key Status/Updates:

  • YP 2.7.3 and 3.0.2 have been released.
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • We are now past M3 feature freeze. A number of key issues have been addressed, thanks to everyone who contributed:
    • psplash systemd race issues fixed (Thanks Scott)
    • make mips issue root caused and glibc fix pulled in (Thanks Victor/Khem)
    • ltp upgrade resolved (Thanks Petr)
    • util-linux update resolved (Thanks Pierre-Jean)
    • Uninative tumbleweed issue resolved (Thanks Michael)
    • libgpg-error upgrade (Thanks Alex)
  • There were many other fixes and upgrades, thanks all!
  • The remaining issues we need to look at addressing before we build M3 are:
    • bind upgrade (needs libuv maintainer fix and resend from Armin)
    • coreutils ptest blocked on libmodule-build-perl reproducibility issue
    • Locked signature selftest failure
    • SystemExit() intermittent selftest failure
    • pseudo sysroot high priority bug
    • gcc buildtools tarball solution for centos7 support
  • Recipe upgrades are now much less likely to be accepted unless there is a pressing need, ideally these should be held until 3.1 is released and development for 3.2 is started. We do not have a tracking branch for 3.2 as we’d like to focus people on 3.1 right now.
  • Bug metrics are not good with a rise in WDD when typically it should be falling for this point in a release cycle.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 3.0.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status February 25, 2020

Current Dev Position: YP 3.1 M3 - At Feature Freeze
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

Key Status/Updates:

  • YP 2.7.3 rc1 is in QA with the report due next week.
  • YP 3.0.2 rc2 was rebuilt to remove a broken bash CVE patch, rc3 had automated QA only and is now due for release.
  • We are now at the date for M3 which is feature freeze. We are not yet in a position where we can build M3 as there are a number of open high blocking bugs but patches will need to start tapering down to bug fix only. More invasive or unplanned features will no longer be accepted.
  • We have a serious issue with hashequiv but a patch in progress for that. There is also a usability issue raised with hashequiv and this can only realistically be fixed in M4, it means changing the UI message handling within bitbake.
  • We continue to see automated test failures with master, most are long standing issues which we’re struggling to resolve. A minority now have had their causes narrowed down or are now reproducible at will which should help but there is concern about the others.
  • Some recent changes like psplash systemd support have introduced a race causing intermittent build failures. We had thought those resolved but they reappeared after merging.
  • Alex Kanavin has quietly but very effectively been fixing ptest failures and we now have only a very small number of non-toolchain tests failing, thanks Alex!
  • We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 2.7.3 built and in QA
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 release soon
  • YP 3.0.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status February 18, 2020

Current Dev Position: YP 3.1 M3
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

Key Status/Updates:

  • The project recently updated its git hosting infrastructure and there were some issues encountered with the cgit http/https repository sharing. Those issues should now be resolved, apologies if they caused issues for anyone. The git:// protocol sharing was unaffected.
  • YP 3.0.2 rc2 is in QA with the report due soon.
  • We continue to see a small number of reproducibility issues with master which need resolving for green builds (in particular gstreamer and perl).
  • A significant memory usage issue was identified during bitbake parsing where memory usage would grow in each parser thread linearly per number of recipes parsed. This would therefore particularly affect large numbers of layers, multilibs and multiconfig. The fix has merged into bitbake along with the corresponding zeus and warrior branches. For one test case it reduced peak memory usage during parsing for 5 multiconfigs from 20GB to 2GB.
  • Warrior patches for 2.7.3 are out for review.
  • With the git infrastructure issue updated, we now have centos8 workers added to the autobuilder.
  • We are making various queued changes to the autobuilder configuration to fix bugs, improve efficiency and test coverage but this may result in some test result instability as we test and resolve issues.
  • We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 2.7.3 built and in QA
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status February 11, 2020

Current Dev Position: YP 3.1 M3
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

Key Status/Updates:

  • YP 3.1 M2 was released
  • We’re now in a much better position with reproducibility issues after around 20 patches merged addressing various problems. Some issues still remain but the bulk of the issues appear to be under control now.
  • Due to the number and type of fixes found, the 3.0.2 rc1 build will be abandoned and rc2 built with the reproducibility fixes (as well as additional hashserv/multiconfig fixes). This delays 3.0.2 by a week but for a reasonable set of improvements.
  • YP 3.0.2 should therefore enter QA within the next day or so.
  • Review of newly queued warrior (2.7.3) patches will happen later this week once 3.0.2 is in QA.
  • With the new fixes and a small fix to the autobuilder code, we managed the first green “full” build in nearly three months.
  • The incoming patch queue is roughly under control again
  • We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
  • One worrying metric is that the WDD is now on level with the high of 2017 so our worst defect weighting in two years. This is sadly unsurprising and directly correlated to a lack of participation in the triage process and a lack of people working on general bug fixing.
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 2.7.3 build date 2/10/2020
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status February 4, 2020

Current Dev Position: YP 3.1 M3
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

Key Status/Updates:

  • YP 3.1 M2 is due to be released with reservations.
  • There are significant concerns with M2 due to the build build reproducibility failures which continue to cause major problems with master too. These will have to block the M3 build/release.
  • The NPM fetcher rework patches have now merged, we’d like to thank Jean-Marie Lemetayer for his patience whilst they were made into good shape with regression tests, thanks, its a good end result.
  • The host dependencies on makeinfo and pod2man have now been dropped to simplify build dependencies and improve reproducibility.
  • The mpc8315e-rdb machine/BSP has been dropped from meta-yocto-bsp.
  • Build reproducibility issues have been tracked down to a number of causes but many more remain, some with open bugs, some with bugs yet to be filed. Any assistance with reproducibility issues is appreciated as is the major factor blocking patch merging at present.
  • Reproducibility failure debugging has been improved with better integration into the autobuilder to assist with this. Saved problematic output is now saved at: https://autobuilder.yocto.io/pub/repro-fail/
  • Ongoing kernel issues still prevent kernel upgrades merging at present but work on debugging the issues is moving forward (thanks Victor/Cisco in particular)
  • We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
  • We have created a “documentation” list and a “licensing” list on the yocto project mailing list infrastructure. We believe these topics would benefit from dedicated discussions, the people involved usually aren’t interested in bulk email as would be found on other lists. The new lists can be found at: https://lists.yoctoproject.org/g/licensing/join and https://lists.yoctoproject.org/g/docs/join
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M2 should release shortly
  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 2.7.3 build date 2/10/2020
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status January 28, 2020

Current Dev Position: YP 3.1 M3
Next Deadline: YP 3.1 M2 in QA - release 1/31/20

Next Team Meetings:

Tip of the Week:

  • The scripts in ${WORKDIR}/temp/run.XXX for shell tasks can be quickly hacked and used for standalone debugging by replacing the function call at the end with “bash -i” which will then drop you into a shell environment matching the task being debugged (minus the fakeroot context).
  • Bonus marks for anyone sending a patch to add the fakeroot context as comments at the start of the scripts.
  • (anyone with tips they’d like to see here, please send to Stephen or Richard)

Key Status/Updates:

  • YP 3.1 M2 is in QA but has issues with build reproducibility
  • We’re unlikely to rebuild M2 as master has the same issues and they look like they will take a while to resolve.
  • There are now serious problems with the build reproducibility test failures on the autobuilder. We’re not sure why there is a sudden set of problems but they are real issues and causing most builds to fail. The tests will have to be disabled unless they can be resolved quickly. There are fixes merged for the CONFIG_SHELL issue and kbd and patches queued as a potential fix for makeinfo. There are more remaining issues, some have open bugs, others don’t have bugs yet. Help with any of these would be appreciated (or help filing the bugs).
  • We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
  • We have created a “documentation” list and a “licensing” list on the yocto project mailing list infrastructure. We believe these topics would benefit from dedicated discussions, the people involved usually aren’t interested in bulk email as would be found on other lists. The new lists can be found at: https://lists.yoctoproject.org/g/licensing/join and https://lists.yoctoproject.org/g/docs/join
  • There is continued concern about the number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
  • We continue to struggle to get clean ‘full’ builds due to the reproducibility issues in particular.
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M2 release date 1/31/2020
  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 2.7.3 build date 2/10/2020
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status January 21, 2020

Current Dev Position: YP 3.1 M2
Next Deadline: YP 3.1 M2 build date 1/20/2020

Next Team Meetings:

Tip of the Week:

  • ‘You can quickly test a change to a recipe on a target by rebuilding it alone, then rsyncing pieces of WORKDIR/image/ or WORKDIR/packages-split/PACKAGENAME/ rather than rebuilding the image (bit of a hack but effective).
  • (anyone with tips they’d like to see here, please send to Stephen or Richard)

Key Status/Updates:

  • YP 3.1 M2 will build shortly, the only remaining blocking issue is the buildtools-extended-tarball fixes which should happen today.
  • Python 2 has been finally removed from OE-Core. This was long scheduled and whilst its causing problems for other layers, we really need to resolve those issues now rather than later in the release cycle so it is the right time to finally do this.
  • Patch merging continues to be making good progress and staying roughly up to date.
  • The patch metrics showed significant improvement this week, partly from continuing work done by Alex Kanavin in keeping things up to date but also from the python2 removal.
  • Bruce is struggling to get the 5.4 kernel to work on all platforms and any help, particularly with MIPS would be much appreciated. This is blocking the kernel updates at this point.
  • We’re starting to see problems as distros enable seccomp in file which then conflicts with our use of pseudo. We need to come up with a better fix but for now, a wrapper script which adds “-S” to the command line for file, injected into PATH is a workaround.
  • There is continued concern about the number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
  • There is a separate email about buildtools tarballs continuing toolchains to support building on wider combinations of host distros, please see that for more info if interested in this.
  • We continue to struggle to get clean ‘full’ builds.
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M2 build date 1/20/2020
  • YP 3.1 M2 release date 1/31/2020
  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 2.7.3 build date 2/10/2020
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status January 14, 2020

Current Dev Position: YP 3.1 M2
Next Deadline: YP 3.1 M2 build date 1/20/2020

Next Team Meetings:

Tip of the Week:

  • ‘oe-pkgdata-browser’ is a new handy small helper UI added by Ross to visualise the pkgdata held within a build.
  • (anyone with tips they’d like to see here, please send to Stephen or Richard)

Key Status/Updates:

  • YP 3.1 M2 is due to be built next week.
  • Patch merging is roughly on track however there are a number of failures identified with key patches (glibc has a prelink issue on mips, python 3.8 upgrade blocked on uid issue, gstreamer meson transition blocked on nodistro failure). Most of these issues are making progress over time.
  • The more worrying aspect is that there are a number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
  • Looking at the build history, “full” images have built cleanly only once in the past month (3 times in the last two months), which is a pretty shocking statistic which summarises the challenges we face there. Most of these are being procrastinated on by the bug owners since we can’t reproduce them at will. We really need help working on these kinds of issues.
  • We have changed the sstate mirrors to be per release, simply to lower the numbers of files in any given sstate directory.
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M2 build date 1/20/2020
  • YP 3.1 M2 release date 1/31/2020
  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 2.7.3 build date 2/10/2020
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Yocto Project Weekly Status January 7, 2020

Current Dev Position: YP 3.1 M2
Next Deadline: YP 3.1 M2 build date 1/20/2020

Next Team Meetings:

Key Status/Updates:

  • YP 3.1 M1 was released.
  • Over the last two weeks there were a number of significant fixes for hash equivalence which should resolve some of the long standing bugs reported here. Some of these fixes may require further architectural tweaks to the codebase but those are cleanups which can happen in due course now the root causes are identified.
  • There are performance issues that remain in hashequivlence but these will be looked at only once the correctness issues and intermittent test failures are addressed.
  • There are some puzzling selftest failures that remain, in particular a locked signatures one which seems to be caused through bad interaction with the hash equivalence code but is intermittent and does not make sense.
  • The patch queue for master should be roughly up to date which some key changes such as the gettext upgrade having merged recently. Some pending changes like the glibc upgrade look problematic.
  • A key functionality change has merged this week where the layout of the sstate directory has changed. This was done to try and improve performance and handle some performance issues where the previous code simply wasn’t scaling. There is no user visible impact but it does mean new sstate will be generated into a new layout and the older sstate will be ignored. The sstate filename length issues should also be addressed by this patchset.
  • Whilst the SWAT process is disbanded, the effect of this is that Richard now has to file the bugs personally. This distracts from other things that could be worked on.
  • The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.
  • The TSC is working on LTS plans, productive discussions have been had and a new policy on handling this and stable releases should be available in the coming weeks.
  • We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M2 build date 1/20/2020
  • YP 3.1 M2 release date 1/31/2020
  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 2.7.3 build date 2/10/2020
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 build date 2/3/2020
  • YP 3.0.2 release date 2/14/2020

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=2020_Yocto_Project_Weekly_Status_Archive&oldid=82145"