Weekly Status: Difference between revisions

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


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Sept. 24th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday Oct. 1st 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. 22th at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Sept. 29th 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 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).
*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.
*We plan to build 3.1.3 imminently
*YP 3.1.3 is currently going through QA.
*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!
*Unfortunately intermittent autobuilder issues, whilst reduced, do still remain.
*The new documentation can be seen at  https://docs.yoctoproject.org/,
*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.
*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.
*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
*Two of the three significant autobuilder issues mentioned last week remain:
*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.
**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:'''<br/>
'''Ways to contribute:'''<br/>
Line 27: Line 23:


'''YP 3.2 Milestone Dates:'''<br/>
'''YP 3.2 Milestone Dates:'''<br/>
*YP 3.2 M3 is out of QA and will be rebuilt
*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 build date 2020/10/5
*YP 3.2 M4 Release date 2020/10/30
*YP 3.2 M4 Release date 2020/10/30


'''Planned upcoming dot releases:'''<br/>
'''Planned upcoming dot releases:'''<br/>
*YP 3.1.3 build date 2020/9/14
*YP 3.1.3 is built and in QA
*YP 3.1.3 release date 2020/9/25
*YP 3.1.4 build date 2020/11/2
*YP 3.1.4 build date 2020/11/2
*YP 3.1.4 release date 2020/11/13
*YP 3.1.4 release date 2020/11/13


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2469 (last week 2466) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2481 (last week 2469) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1268 (last week 1258)
**Total patches found: 1270 (last week 1268)
**Patches in the Pending State: 496 (39%) [last week 496 (39%)]
**Patches in the Pending State: 493 (39%) [last week 496 (39%)]


'''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:44, 29 September 2020

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

Archives

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