Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status Oct. 20, 2020 ==
== Yocto Project Weekly Status Oct. 20, 2020 ==
Current Dev Position: YP 3.2 M4<br/>
Current Dev Position: YP 3.2 Final Build<br/>
Next Deadline: YP 3.2 M4 Feature Freeze - Now<br/>
Next Deadline: YP 3.2 M4 Feature Freeze - Now<br/>


Line 10: Line 10:


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1.3 has been released.
*YP 3.2 rc1 is currently building on the autobuilder.
*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..
*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.
*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.
*We have a steadily riding WDD and Medium+ bug count which is a concern.
*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!
*We realized there was an issue with wiki account creation. These should be created now but please report if there are any 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.
*A 3.3 planning document has been created for ideas about what may happen in the 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 3.3 milestones and release.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 22: Line 23:


'''YP 3.2 Milestone Dates:'''<br/>
'''YP 3.2 Milestone Dates:'''<br/>
*YP 3.2 M4 build date 2020/10/5
*YP 3.2 M4 building now.
*YP 3.2 M4 Release date 2020/10/30
*YP 3.2 M4 Release date 2020/10/30


Revision as of 14:43, 20 October 2020

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 3.3 planning document has been created for ideas about what may happen in the 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 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

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=79390"