Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status Sept. 8, 2020 ==
== Yocto Project Weekly Status Sept. 156, 2020 ==
Current Dev Position: YP 3.2 M3<br/>
Current Dev Position: YP 3.2 M3<br/>
Next Deadline: YP 3.2 M3 Feature Freeze - Now<br/>
Next Deadline: YP 3.2 M3 Feature Freeze - Now<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Sept. 10th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday Sept. 17th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Tuesday Oct. 6th 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. 15th at 8am PDT (https://zoom.us/j/990892712)
*Twitch -  See https://www.twitch.tv/theyoctojester
*Twitch -  See https://www.twitch.tv/theyoctojester


'''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.
*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.
*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 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).
*There are three significant autobuilder issues being faced currently:
*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.
**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
*There have also been significant cleanups to the server process logging and reporting of processes holding the bitbake lock.
**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 work in enabling PRServ to work well with hash equivalence has merged.
**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
*A preview of the sphinx built documentation is now available at https://docs.yoctoproject.org/, work is ongoing to complete the migration work.
*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.
*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
*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:'''<br/>
'''YP 3.2 Milestone Dates:'''<br/>
Line 32: Line 32:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2461 (last week 2436) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2466 (last week 2461) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1254 (last week 1264)
**Total patches found: 1258 (last week 1254)
**Patches in the Pending State: 496 (40%) [last week 502 (40%)]
**Patches in the Pending State: 496 (39%) [last week 496 (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:57, 15 September 2020

Yocto Project Weekly Status Sept. 156, 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

Archives

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