Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 4: Line 4:


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Sept. 3rd at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday Sept. 10th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Tuesday Sept. 1st at 8am  PDT (https://zoom.us/j/990892712)
*Monthly Project Meeting Tuesday Oct. 6th at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Sept. 8th at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Sept. 8th at 8am PDT (https://zoom.us/j/990892712)
*Twitch -  See https://www.twitch.tv/theyoctojester
*Twitch -  See https://www.twitch.tv/theyoctojester
Line 11: Line 11:
'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*M3 has now closed and we’re at feature freeze for 3.2.
*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.
*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.
*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.
*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).
*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.
*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 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.
*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.
*We will process one last round of recipe upgrades before we build M3.
*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.
*A preview of the sphinx built documentation is now available at https://docs.yoctoproject.org/, work is ongoing to complete the migration work.
*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
*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.
*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
*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.
*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:'''<br/>
'''YP 3.2 Milestone Dates:'''<br/>
Line 33: Line 33:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2436 (last week 2424) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2461 (last week 2436) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1264 (last week 1273)
**Total patches found: 1264 (last week 1264)
**Patches in the Pending State: 502 (40%) [last week 502 (39%)]
**Patches in the Pending State: 502 (40%) [last week 502 (40%)]


'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>

Revision as of 14:45, 8 September 2020

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.
  • 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.
  • We will process one last round of recipe upgrades before we build M3.
  • 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

Archives

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