From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pg1-f195.google.com (mail-pg1-f195.google.com [209.85.215.195]) by mx.groups.io with SMTP id smtpd.web11.349.1600786306656723872 for ; Tue, 22 Sep 2020 07:51:46 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=AfXvtCOU; spf=pass (domain: gmail.com, ip: 209.85.215.195, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pg1-f195.google.com with SMTP id g29so12163248pgl.2 for ; Tue, 22 Sep 2020 07:51:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version:content-language :thread-index; bh=i50tCVzDojkDTSlrNMypJ2tkkfHbWj3rsMyNIOJIB9o=; b=AfXvtCOUMEGSmVN9GeLksGHmFZzxIPE3YmItjCDdfWlbwiq25WU4GKSh1vJ6/Mekqh CmOUz6lq8I2MVsN9S9EPwA+rdEvCkEm8pMnOcG4retuuVAi4upm/KoO2Zk9pEItbmFSV N8JCYxtoz9c8rgfyyC9kFoeknBeJi1rrzMolOyMKIOTHTk4XXDvg+DL2lolf6T+oUTWe 4oK1O9v+nemFetIv8WweFlztNgCYJpr0lpLhEBFmO5Sc0BEGtbIx+PwiYzukSyy+m9lu 5Un8QvJFrBRpBYnc2Uf4qICS6Zhoj6CCbeYnD5YEWpl3xQ0zQGFM6jN5pKzjPdQj75WU xuiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-language:thread-index; bh=i50tCVzDojkDTSlrNMypJ2tkkfHbWj3rsMyNIOJIB9o=; b=S17SJ3nWyc7E5KWmtIy7AXDVNoTDwuJl1ztEnsMdFFi0HzsdUYO4l3YrKa8O6p+L5f SzlAD4IJmiMvTbB0xCMzbkUodcn5UqQGfQcnxyVajmXXp8TQLJ/qokG9+DM/7YCxhfIQ u9mRyLP/ucIlFOa4795pJLkb2X8CPgrxNhyevx4TvBn5Ikc1SMwbpm7lUUZ1eG9SXqzy KN/XVL9OorDnfAN3FcsxINaYR2menkxNILsonuZ8pfd1O/Ryfv5rjWa/FrMDc+Oftx69 tT1EBMI3omf0mlgss+NqtGRUFQFKI0A/A6esNUzBt8Rb4OElaF6udkOkjI38b7CKkKPH HP3Q== X-Gm-Message-State: AOAM532k3O+prVTIb3q8aqjp53smmU0oxcbbiJ8RyN6gu+pPPtKgHti5 fMEXyBNowvQ3Zxd3MyZhpoQ= X-Google-Smtp-Source: ABdhPJxMF56Zw/05V4DAnpX+mvKFTNd7jE445pjFo61dqfzd64nhJJDu88QSFBQ7NGP4D2sQ1PYa4w== X-Received: by 2002:a17:902:522:b029:d1:9bc8:15df with SMTP id 31-20020a1709020522b02900d19bc815dfmr5146461plf.25.1600786305995; Tue, 22 Sep 2020 07:51:45 -0700 (PDT) Return-Path: Received: from skjolley (wsip-184-183-149-66.ph.ph.cox.net. [184.183.149.66]) by smtp.gmail.com with ESMTPSA id k5sm15244845pfu.77.2020.09.22.07.51.44 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 22 Sep 2020 07:51:45 -0700 (PDT) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW38'20 Date: Tue, 22 Sep 2020 07:51:44 -0700 Message-ID: <04f501d690ef$e45fdec0$ad1f9c40$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdaQ79NqTa9gEE/1RtyyBAdszKbHnQ== Content-Type: multipart/alternative; boundary="----=_NextPart_000_04F6_01D690B5.3802DB80" Content-Language: en-us ------=_NextPart_000_04F6_01D690B5.3802DB80 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.2 M4 Next Deadline: YP 3.2 M4 Feature Freeze - Now Next Team Meetings: * Bug Triage meeting Thursday Sept. 24th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Oct. 6th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Sept. 23th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - See https://www.twitch.tv/theyoctojester 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: * There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers * There are bugs that are currently unassigned for YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhan cements.2FBugs * We'd welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main tainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to "Unassigned" soon to help facilitate this. 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: * WDD 2469 (last week 2466) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1268 (last week 1258) * Patches in the Pending State: 496 (39%) [last week 496 (39%)] The Yocto Project's technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status [If anyone has suggestions for other information you'd like to see on this weekly status update, let us know!] Thanks, Stephen K. Jolley Yocto Project Program Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_04F6_01D690B5.3802DB80 Content-Type: text/html; boundary="----=_NextPart_000_1263_01D68B36.3AAA6A30"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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?qui= cksearch=3DAB-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.yocto= project.org/wiki/TSC

 

The Status reports = are now stored on the wiki at: https://wiki.yocto= project.org/wiki/Weekly_Status

 

[If anyone has = suggestions for other information you’d like to see on this weekly = status update, let us know!]

 

Thanks,

 

Stephen K. Jolley<= o:p>

Yocto = Project Program Manager

(    Cell:         = ;       (208) = 244-4460

* Email:           = ;   sjolley.yp.pm@gmail.com

 

------=_NextPart_000_04F6_01D690B5.3802DB80--