From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pg1-f172.google.com (mail-pg1-f172.google.com [209.85.215.172]) by mx.groups.io with SMTP id smtpd.web12.15609.1600182008427946786 for ; Tue, 15 Sep 2020 08:00:08 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=owk/A52C; spf=pass (domain: gmail.com, ip: 209.85.215.172, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pg1-f172.google.com with SMTP id l191so2128860pgd.5 for ; Tue, 15 Sep 2020 08:00:08 -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=jdkQqlbd6WoyXKmnpwjjTemDEdszEZEkI8pAslmz76E=; b=owk/A52CdSpAkAB9NqkxNMVVNV79083tKKL312lb1lh9yCovmb46G3HqLgkoZavlsD fmbn4FrQI5y4fcQEkD6M2D0xAFi5w8GgqGO2L/Z/MfKaJU9gDShP84F02Mf88ZeyeqjL n6aGkXsoiIVhsCxjQku46NA+ZY0LWPDzDYnc+sex4XMn2/0OWM4xbKeOFnT0QNpl9lvS +yvNnM+afUhdOOBnRDDcytYUbj4l57VE3INgAPcNkxhMfqytTQAZKxfANIxan3aPym/A eNXwmVxkm9BXZiEgF/ICvRhvxpdUvACOHjftbAH+CPdBBgJ+p9mLmfbwO8Hz8SaqRYlC 4PMw== 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=jdkQqlbd6WoyXKmnpwjjTemDEdszEZEkI8pAslmz76E=; b=Qw3V6FRuKDTgNC55/wbhqKnSTS4AeBVrDiIBUX9QuFsb+I3uEp54d0yJryMWTj7PoQ w/bG9eRI5M0mvdo75reP27UvyE/LSZ/h+dtSpXh45ww6nbsaQ5TSZMtmhBOZ2hfzaVv0 Ia6cA96E3o/Okx7EEa3jxo/zOP3hb0kKL0CRCyWW1BnesajaxzjsckBdnBFrCCkFWYfC ErGs/P+AUMj2iZJJ0ok2fVlKmI9ttwwDReq23CzXe3VDetm1eiBgXEpKTLthwzgcjHDD ZHrNxFriwINfCvbpakG3Vo5ElffQUDtTmbOzhw1n3QmAlHWl69wSLx+Ui07claGkUzk5 /u8w== X-Gm-Message-State: AOAM533uPMlJhXWIeym6ypfVZuhBJOube2y3T8NtgNV2FNCiKsImGd3Q KP5F51FzQ82hbB3zGptTW+4= X-Google-Smtp-Source: ABdhPJw1d8GILHJ5q6X45qwzv0cUX/uDBEWkwt0mgjOF09sTe9/z7X3g1aZTfJW7i4OZU0iPNm4TNw== X-Received: by 2002:a63:5a48:: with SMTP id k8mr15149039pgm.62.1600182007913; Tue, 15 Sep 2020 08:00:07 -0700 (PDT) Return-Path: Received: from skjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id 187sm13846937pfx.174.2020.09.15.08.00.07 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Sep 2020 08:00:07 -0700 (PDT) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW37'20 Date: Tue, 15 Sep 2020 08:00:06 -0700 Message-ID: <126201d68b70$e703c3f0$b50b4bd0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdaLcN1a7zdw6WbdS3W9My5PMFWJmA== Content-Type: multipart/alternative; boundary="----=_NextPart_000_1263_01D68B36.3AAA6A30" Content-Language: en-us ------=_NextPart_000_1263_01D68B36.3AAA6A30 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.2 M3 Next Deadline: YP 3.2 M3 Feature Freeze - Now Next Team Meetings: * 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) * Weekly Engineering Sync Tuesday Sept. 15th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - See https://www.twitch.tv/theyoctojester 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_Enhan cements.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: * WDD 2466 (last week 2461) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1258 (last week 1254) * 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: 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_1263_01D68B36.3AAA6A30 Content-Type: text/html; boundary="----=_NextPart_000_0763_01D68033.E3F21970"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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?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.

 

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.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_1263_01D68B36.3AAA6A30--