From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f195.google.com (mail-pf1-f195.google.com [209.85.210.195]) by mail.openembedded.org (Postfix) with ESMTP id 6BA747D435 for ; Tue, 9 Apr 2019 14:55:04 +0000 (UTC) Received: by mail-pf1-f195.google.com with SMTP id 10so9857015pfo.5 for ; Tue, 09 Apr 2019 07:55:05 -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=km/UmrzQORV/nzuoGykhkiMi0M9rCa7nsu4WtdvPGnw=; b=Igl6wv0jc87XvyPIfN4QLBt7jkWfgrfuWN167DOpFOiu78YoWMoADZOzM1QXsQMals BWqvm2EMiWll6c2VOtFBDMLHeXGHIB0/xakwR1D7cBYeBbXWdUlostfZZfZ6o/clU9L6 oqRxW2azEdwplGhk4ObWYTkqXCQvLyzPq1udhFrVSXjFgLc0J7Sh1WfVfDe6w36RUkHX D3CKWLdqJC6X2s2PYjEFR4hWKKzYM4ho+8QMTYyLo3XWwI1JQM2RGEXj4wYj9ITDtmVs wMOC19Fy3VCx1s5WxozeRk3I1GM7AdMeAJLviCY3LGvzosrng1dhgQ0BiV21wH0/05rG 5fuw== 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=km/UmrzQORV/nzuoGykhkiMi0M9rCa7nsu4WtdvPGnw=; b=lzBQ0/8cyyVbNh7j2NXohsCiif6i+tmzkefmVgqAzGxlSfn/UqpNgtACTi4MhTMFhd 9qEZS0AIdsdarVp+kxnCp2rzzToVkaGZe0sNaXHLCdgTYK3g5WvlCMtYSnzUWEwxB5nh xSD67fwEb2WjZT65MghDGz2O+hAk4MD+6bjjCQGhU7dX47g4wJ8l+byKypC7cY9ktPJd LMVqTvJXSKRuUai+Cc/vswaL38g/yrf0Be4mIihLbKY/xEwnIFRsE/wwan2s+b/ttbpj WpnDr4L/UBeA7MLDr8xEOsPLG82qDTB1+1YSI+vka9a9CUKnK1LZUl2Hvu7j6blziZbk 7y6w== X-Gm-Message-State: APjAAAWvbS25SSsE/iQqKPdlozSm8j17elycFRpny5hA1dvlaoyqDm+N U4wO/fHTPV3DAMFW6dpOmlI= X-Google-Smtp-Source: APXvYqxkDBEns6NQstW1jryL7lUxEJwoq4oabo6Q4ooGTL15KctB9pPqa9GwSLoXTDWPNw4miAE5sw== X-Received: by 2002:a63:7943:: with SMTP id u64mr34786860pgc.91.1554821705092; Tue, 09 Apr 2019 07:55:05 -0700 (PDT) Received: from sjolley (wsip-70-166-100-47.ph.ph.cox.net. [70.166.100.47]) by smtp.gmail.com with ESMTPSA id e126sm77498097pfh.35.2019.04.09.07.55.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Apr 2019 07:55:04 -0700 (PDT) From: To: , Date: Tue, 9 Apr 2019 07:55:03 -0700 Message-ID: <022e01d4eee4$373c2630$a5b47290$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJshvhVi5wpRWBd+HywYJuFAw7TYg== Subject: Yocto Project Status WW14'19 X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Apr 2019 14:55:04 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_022F_01D4EEA9.8ADEFBE0" Content-Language: en-us ------=_NextPart_000_022F_01D4EEA9.8ADEFBE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 2.7 M4 (New feature Freeze has begun.) Next Deadline: YP 2.7 M3 Release Target was Mar. 8, 2019 and it should release today! SWAT Team Rotation: * SWAT lead is currently: Amanda * SWAT team rotation: Amanda -> Chen on Apr. 12, 2019 * SWAT team rotation: Chen -> Armin Apr. 19, 2019 * https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Next Team Meetings: * YP 2.8 Planning meeting Tuesday April 16nd at 8am PDT ( https://zoom.us/j/990892712) * Bug Triage meeting Thursday April 11th at 7:30am PDT ( https://zoom.us/j/454367603) Key Status/Updates: * YP 2.7 M3 rc1 will be released today. The YP 2.7 M3 rc1 report is summarized at https://lists.yoctoproject.org/pipermail/yocto/2019-April/044667.html and the results are at https://autobuilder.yocto.io/pub/releases/yocto-2.7_M3.rc1/testresults/. * YP 2.5.3 and YP 2.6.2 stable releases were built and have been submitted to QA * YP 2.6.2 is currently going through the QA process with YP 2.5.3 queued behind it. * Process issues in the way ptest was being processed by QA have been discovered which mean the previous ptest results are not comparable with the new QA process. For consistency going forward we will be using the new QA process as the definitive results and will be comparing for regressions based upon these. * The "warrior" branches for 2.7 have been created and the metadata updated, patches are being slowed in line with release stablisation with increasingly critical fixes only. * The remaining things which are planned for YP 2.7 M4 before we have the final 2.7 rc1 build are: * Upgrading -tiny to the 5.0 linux-yocto kernel (currently 4.18) * Removal of the 4.18 kernel * Fixing the python3 ptest timeout and result status issues * Fixing some of the util-linux ptest failures * Potentially integrating a key and long time puzzling pseudo issue * Integrating qemumips shutdown issues identified in the kernel * Continue to investigate python3 testsuite hang on 5.0+ kernels (trying to get help upstream) * Worrying things which we don't have good plans for currently (mainly lack of people to help with): * Intermittent autobuilder failures (fork running out of resources - which resources?, oe-selftest intermittent issues, gpg signing resource problems, occasional PR server failure and more) * Build-appliance testing issues (show up on each QA report across multiple releases) * 40% valgrind ptest failures * Known bitbake memory resident bugs * Other ptest failures * The 2.8 planning discussions are starting and there is a google doc summarising the discussions so far: https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJG XbU/ If people are planning to work on specific things in 2.8 please let us know so we can incorporate this into our plans. If you're interested in working on anything in the document, please also let us know or talk with us in one of the planning meetings. Planned Releases for YP 2.7: * YP 2.7 M4 Cutoff was Apr. 1, 2019 * YP 2.7 M4 Release Target is Apr. 26, 2019 Planned upcoming dot releases: * YP 2.5.3 (Sumo) is in QA. * YP 2.6.2 (Thud) is in QA. Tracking Metrics: * WDD 2471 (last week 2442) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1553 (last week 1542 * Patches in the Pending State: 655 (42%) [last week 656 (42%)] Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features 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 Project Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_022F_01D4EEA9.8ADEFBE0 Content-Type: text/html; boundary="----=_NextPart_000_0319_01D4E929.15A39500"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 2.7 M4 (New feature Freeze has = begun.)

Next Deadline: YP = 2.7 M3 Release Target was Mar. 8, 2019 and it should release = today!

 

SWAT Team = Rotation:

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 2.7 M3 rc1 will be released = today. The YP 2.7 M3 rc1 report is summarized at https://lists.yoctoproject.org/pipermail/yocto/20= 19-April/044667.html and the results are at https://autobuilder.yocto.io/pub/releases/yocto-2= .7_M3.rc1/testresults/.
  • YP 2.5.3 and YP 2.6.2 stable = releases were built and have been submitted to = QA
  • YP 2.6.2 is currently going = through the QA process with YP 2.5.3 queued behind it. =
  • Process issues in the way ptest = was being processed by QA have been discovered which mean the previous = ptest results are not comparable with the new QA process. For = consistency going forward we will be using the new QA process as the = definitive results and will be comparing for regressions based upon = these.
  • The “warrior” = branches for 2.7 have been created and the metadata updated, patches are = being slowed in line with release stablisation with increasingly = critical fixes only.
  • The remaining things which are = planned for YP 2.7 M4 before we have the final 2.7 rc1 build = are:
    • Upgrading -tiny to the 5.0 = linux-yocto kernel (currently 4.18)
    • Removal of the 4.18 = kernel
    • Fixing the python3 ptest = timeout and result status issues
    • Fixing some of the util-linux = ptest failures
    • Potentially integrating a key = and long time puzzling pseudo issue
    • Integrating qemumips shutdown = issues identified in the kernel
    • Continue to investigate python3 = testsuite hang on 5.0+ kernels (trying to get help = upstream)
  • Worrying things which we = don’t have good plans for currently (mainly lack of people to help = with):
    • Intermittent autobuilder = failures (fork running out of resources - which resources?, oe-selftest = intermittent issues, gpg signing resource problems, occasional PR server = failure and more)
    • Build-appliance testing issues = (show up on each QA report across multiple = releases)
    • 40% valgrind ptest = failures
    • Known bitbake memory resident = bugs
    • Other ptest = failures
  • The 2.8 planning discussions = are starting and there is a google doc summarising the discussions so = far: https://docs.google.com/document/d/1CNEKA4d0eT6-e= 0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/

If people are = planning to work on specific things in 2.8 please let us know so we can = incorporate this into our plans. If you’re interested in working = on anything in the document, please also let us know or talk with us in = one of the planning meetings.

 

Planned Releases = for YP 2.7:

  • YP 2.7 M4 Cutoff was Apr. 1, = 2019
  • YP 2.7 M4 Release Target is = Apr. 26, 2019

 

Planned upcoming = dot releases:

  • YP 2.5.3 (Sumo) is in = QA.
  • YP 2.6.2 (Thud) is in = QA.

 

Tracking = Metrics:

 

Key Status Links = for YP:

https://wiki.yoctoproject.or= g/wiki/Yocto_Project_v2.7_Status

https://wiki.yoctoproject.or= g/wiki/Yocto_2.7_Schedule

https://wiki.yoctoproject.or= g/wiki/Yocto_2.7_Features

 

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 Project Manager

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

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

 

------=_NextPart_000_022F_01D4EEA9.8ADEFBE0--