From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com [209.85.214.178]) by mail.openembedded.org (Postfix) with ESMTP id 6FAA661132 for ; Tue, 18 Feb 2020 16:09:38 +0000 (UTC) Received: by mail-pl1-f178.google.com with SMTP id y1so8251381plp.7 for ; Tue, 18 Feb 2020 08:09:39 -0800 (PST) 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=e6WinSmE8d+Iu9d26JaPmnCoCFEP9qx/mMhTqLOpcmM=; b=KTf+d29X8xm1NyhMdvc9nTnWqBZy7mtWYglXpAq9Krfsn6uulfyC/xUIzOxzvRpeun H3cS4aWxj7FtiD8WIzeIKkiZlgeJKq/7uw34n291xTF3MEBWSEdNfz9ytnFuEGqEiCwn qU73n8uID7pHlrfifsrLV/05vzqbYvI6et+Ol/kNen2SgPZBK4pnlVhzcxvhtezdUpb5 4c2TkFMzPV89dBKPObew+fES33LOWLGSnF5GuS7pwoPEbBtEISbxK/9K3cqAPakAEhdO fQLUdi3IN97xRzs6CLdx5xs/ZtZxx/3xkoDIN4B7FaEljeiea85MDqfGxVGmzrwX+4Yi sc3w== 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=e6WinSmE8d+Iu9d26JaPmnCoCFEP9qx/mMhTqLOpcmM=; b=asPJaKqoyPuCtnCSSCSTYDGoT412wodOAS7QbE0AkG+q9NdWiq5qozOsxsn8CiaiQ9 eTeSx0uGkLCPqKndwzkO18rglUYeIs3Qc8Fw5wXZodX+a706tmtCoU8F2qqLfoDZj0YQ B5jyncekHdo6p9bjG39EJoIdAN5Q+vd/XM9zKckd8UjUd0xYdNAQgnwwtgvg777hX50H Err12zQGtngokuXMesYXrQCQ4qYX71Mf6ojQLf+XcPWNZgmIf/tmLpPSK6Q9NnEGghu2 MRkd/V6mDcALKMUpcVHuE4muEtta+BkKYOAv7qimvTAdD4UbC3pwnYF7oHbl/6ve5UF3 7Y7A== X-Gm-Message-State: APjAAAVQjCPa/vhBaFk7k/fs0GGwLrxSuFx24IcYI5e3RGepHXvqRlec NM0qiL/NT8clOOyz48u5jcc= X-Google-Smtp-Source: APXvYqw8VypQzQEKNYBia0rOvG8MDW6M0ue7Zjs22rAd9tmJc5Yot3HbrekO6BZdiLYEjnKx1pEy1A== X-Received: by 2002:a17:902:7b86:: with SMTP id w6mr20795604pll.317.1582042179286; Tue, 18 Feb 2020 08:09:39 -0800 (PST) Received: from skjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id j8sm3868265pjb.4.2020.02.18.08.09.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Feb 2020 08:09:38 -0800 (PST) From: To: , Date: Tue, 18 Feb 2020 08:09:38 -0800 Message-ID: <0b8a01d5e675$d2363e30$76a2ba90$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdXmdcUD2UQ7LOb7QeyyPqIozFyarA== Subject: Yocto Project Status WW07'20 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, 18 Feb 2020 16:09:38 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0B8B_01D5E632.C415E460" Content-Language: en-us ------=_NextPart_000_0B8B_01D5E632.C415E460 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M3 Next Deadline: YP 3.1 M3 build date 2/24/2020 Next Team Meetings: * Bug Triage meeting Thursday Feb. 20th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Mar. 3rd at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Feb. 18th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Mar. 10th at 8am PDT ( https://www.twitch.tv/yocto_project) Key Status/Updates: * The project recently updated its git hosting infrastructure and there were some issues encountered with the cgit http/https repository sharing. Those issues should now be resolved, apologies if they caused issues for anyone. The git:// protocol sharing was unaffected. * YP 3.0.2 rc2 is in QA with the report due soon. * We continue to see a small number of reproducibility issues with master which need resolving for green builds (in particular gstreamer and perl). * A significant memory usage issue was identified during bitbake parsing where memory usage would grow in each parser thread linearly per number of recipes parsed. This would therefore particularly affect large numbers of layers, multilibs and multiconfig. The fix has merged into bitbake along with the corresponding zeus and warrior branches. For one test case it reduced peak memory usage during parsing for 5 multiconfigs from 20GB to 2GB. * Warrior patches for 2.7.3 are out for review. * With the git infrastructure issue updated, we now have centos8 workers added to the autobuilder. * We are making various queued changes to the autobuilder configuration to fix bugs, improve efficiency and test coverage but this may result in some test result instability as we test and resolve issues. * We're collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add). * The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated. YP 3.1 Milestone Dates: * YP 3.1 M3 build date 2/24/2020 * YP 3.1 M3 release date 3/6/2020 * YP 3.1 M4 build date 3/30/2020 * YP 3.1 M4 release date 4/24/2020 Planned upcoming dot releases: * YP 2.7.3 built and in QA * YP 2.7.3 release date 2/21/2020 * YP 3.0.2 build date 2/3/2020 * YP 3.0.2 release date 2/14/2020 Tracking Metrics: * WDD 2710 (last week 2728) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1360 (last week 1361) * Patches in the Pending State: 546 (40%) [last week 547 (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_0B8B_01D5E632.C415E460 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M3

Next Deadline: YP = 3.1 M3 build date 2/24/2020

 

Next Team = Meetings:

 

Key = Status/Updates:

  • The project recently updated = its git hosting infrastructure and there were some issues encountered = with the cgit http/https repository sharing. Those issues should now be = resolved, apologies if they caused issues for anyone. The git:// = protocol sharing was unaffected.
  • YP 3.0.2 rc2 is in QA with the = report due soon.
  • We continue to see a small = number of reproducibility issues with master which need resolving for = green builds (in particular gstreamer and = perl).
  • A significant memory usage = issue was identified during bitbake parsing where memory usage would = grow in each parser thread linearly per number of recipes parsed. This = would therefore particularly affect large numbers of layers, multilibs = and multiconfig. The fix has merged into bitbake along with the = corresponding zeus and warrior branches. For one test case it reduced = peak memory usage during parsing for 5 multiconfigs from 20GB to = 2GB.
  • Warrior patches for 2.7.3 are = out for review.
  • With the git infrastructure = issue updated, we now have centos8 workers added to the = autobuilder.
  • We are making various queued = changes to the autobuilder configuration to fix bugs, improve efficiency = and test coverage but this may result in some test result instability as = we test and resolve issues.
  • We’re collecting a list = of companies, products and projects which use the Yocto Project on the = wiki: https://wiki.yoctoproject.org/wiki/Project_Users<= /span> Please add any you know are missing (or email Richard/Stephen = who can add).
  • The triage team is worried = about attendance at triage meetings and the project is finding it hard = to find people to help fix bugs. If anyone is willing to work on bugs, = assistance would be greatly appreciated.

 

YP 3.1 Milestone = Dates:

  • YP 3.1 M3 build date = 2/24/2020
  • YP 3.1 M3 release date = 3/6/2020
  • YP 3.1 M4 build date  = 3/30/2020
  • YP 3.1 M4 release date  = 4/24/2020

 

Planned upcoming = dot releases:

  • YP 2.7.3 built and in = QA
  • YP 2.7.3 release date = 2/21/2020
  • YP 3.0.2 build date  = 2/3/2020
  • YP 3.0.2 release date = 2/14/2020

 

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_0B8B_01D5E632.C415E460-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from yocto-www.yoctoproject.org (yocto-www.yoctoproject.org [140.211.169.56]) by mx.groups.io with SMTP id smtpd.web11.20.1582148694590679741 for ; Wed, 19 Feb 2020 13:44:54 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=KTf+d29X; spf=softfail (domain: gmail.com, ip: 140.211.169.56, mailfrom: sjolley.yp.pm@gmail.com) Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id B8A5FE0174D; Tue, 18 Feb 2020 08:09:42 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (sjolley.yp.pm[at]gmail.com) * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no * trust * [209.85.216.47 listed in list.dnswl.org] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid Received: from mail-pj1-f47.google.com (mail-pj1-f47.google.com [209.85.216.47]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id F3C0BE0174B for ; Tue, 18 Feb 2020 08:09:39 -0800 (PST) Received: by mail-pj1-f47.google.com with SMTP id r67so1226616pjb.0 for ; Tue, 18 Feb 2020 08:09:39 -0800 (PST) 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=e6WinSmE8d+Iu9d26JaPmnCoCFEP9qx/mMhTqLOpcmM=; b=KTf+d29X8xm1NyhMdvc9nTnWqBZy7mtWYglXpAq9Krfsn6uulfyC/xUIzOxzvRpeun H3cS4aWxj7FtiD8WIzeIKkiZlgeJKq/7uw34n291xTF3MEBWSEdNfz9ytnFuEGqEiCwn qU73n8uID7pHlrfifsrLV/05vzqbYvI6et+Ol/kNen2SgPZBK4pnlVhzcxvhtezdUpb5 4c2TkFMzPV89dBKPObew+fES33LOWLGSnF5GuS7pwoPEbBtEISbxK/9K3cqAPakAEhdO fQLUdi3IN97xRzs6CLdx5xs/ZtZxx/3xkoDIN4B7FaEljeiea85MDqfGxVGmzrwX+4Yi sc3w== 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=e6WinSmE8d+Iu9d26JaPmnCoCFEP9qx/mMhTqLOpcmM=; b=Sr5PKmkIzlwfQzxHgjFpu3fHoWhGZghsZ8nUkE5KOoIiZGM0dF0zdLaQuUqYWyP35f LeUMEqLgo0S6AtjWqrfjnXzn7ZEbC4D7ljnpLkrtVh2CHrM6sOoCUlZEux3sZpCES2eE 0vFzVBuIIJ2SjR5kZQPJ3+PmTRGnPEEExqXw2PhQhc12F4aQRIYrC3W74bUFJJeNrYUX 8mWa8cAVd1BA/7PqfJEqpPxmQqJXMOHMx3yj+uhzjXCh2Xh81Rt7WR2oB7ok+Ho3IHKm ZTiOjUOBGG4OWnxDuAMck7Br6A5v0SUiBjlUDJBym6zQxxfFUnkePV1GTXNJ2cDa0M5f uPrg== X-Gm-Message-State: APjAAAVChcemHzcbOMwBbrkQf7gCgJqGGbIG3lXsGXeQuMZsuYzJA1zx Npo2WwFoqw9GCaYwa6sZ4qe73YuO X-Google-Smtp-Source: APXvYqw8VypQzQEKNYBia0rOvG8MDW6M0ue7Zjs22rAd9tmJc5Yot3HbrekO6BZdiLYEjnKx1pEy1A== X-Received: by 2002:a17:902:7b86:: with SMTP id w6mr20795604pll.317.1582042179286; Tue, 18 Feb 2020 08:09:39 -0800 (PST) Received: from skjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id j8sm3868265pjb.4.2020.02.18.08.09.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Feb 2020 08:09:38 -0800 (PST) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW07'20 Date: Tue, 18 Feb 2020 08:09:38 -0800 Message-ID: <0b8a01d5e675$d2363e30$76a2ba90$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdXmdcUD2UQ7LOb7QeyyPqIozFyarA== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0B8B_01D5E632.C415E460" Content-Language: en-us ------=_NextPart_000_0B8B_01D5E632.C415E460 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M3 Next Deadline: YP 3.1 M3 build date 2/24/2020 Next Team Meetings: * Bug Triage meeting Thursday Feb. 20th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Mar. 3rd at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Feb. 18th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Mar. 10th at 8am PDT ( https://www.twitch.tv/yocto_project) Key Status/Updates: * The project recently updated its git hosting infrastructure and there were some issues encountered with the cgit http/https repository sharing. Those issues should now be resolved, apologies if they caused issues for anyone. The git:// protocol sharing was unaffected. * YP 3.0.2 rc2 is in QA with the report due soon. * We continue to see a small number of reproducibility issues with master which need resolving for green builds (in particular gstreamer and perl). * A significant memory usage issue was identified during bitbake parsing where memory usage would grow in each parser thread linearly per number of recipes parsed. This would therefore particularly affect large numbers of layers, multilibs and multiconfig. The fix has merged into bitbake along with the corresponding zeus and warrior branches. For one test case it reduced peak memory usage during parsing for 5 multiconfigs from 20GB to 2GB. * Warrior patches for 2.7.3 are out for review. * With the git infrastructure issue updated, we now have centos8 workers added to the autobuilder. * We are making various queued changes to the autobuilder configuration to fix bugs, improve efficiency and test coverage but this may result in some test result instability as we test and resolve issues. * We're collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add). * The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated. YP 3.1 Milestone Dates: * YP 3.1 M3 build date 2/24/2020 * YP 3.1 M3 release date 3/6/2020 * YP 3.1 M4 build date 3/30/2020 * YP 3.1 M4 release date 4/24/2020 Planned upcoming dot releases: * YP 2.7.3 built and in QA * YP 2.7.3 release date 2/21/2020 * YP 3.0.2 build date 2/3/2020 * YP 3.0.2 release date 2/14/2020 Tracking Metrics: * WDD 2710 (last week 2728) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1360 (last week 1361) * Patches in the Pending State: 546 (40%) [last week 547 (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_0B8B_01D5E632.C415E460 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M3

Next Deadline: YP = 3.1 M3 build date 2/24/2020

 

Next Team = Meetings:

 

Key = Status/Updates:

  • The project recently updated = its git hosting infrastructure and there were some issues encountered = with the cgit http/https repository sharing. Those issues should now be = resolved, apologies if they caused issues for anyone. The git:// = protocol sharing was unaffected.
  • YP 3.0.2 rc2 is in QA with the = report due soon.
  • We continue to see a small = number of reproducibility issues with master which need resolving for = green builds (in particular gstreamer and = perl).
  • A significant memory usage = issue was identified during bitbake parsing where memory usage would = grow in each parser thread linearly per number of recipes parsed. This = would therefore particularly affect large numbers of layers, multilibs = and multiconfig. The fix has merged into bitbake along with the = corresponding zeus and warrior branches. For one test case it reduced = peak memory usage during parsing for 5 multiconfigs from 20GB to = 2GB.
  • Warrior patches for 2.7.3 are = out for review.
  • With the git infrastructure = issue updated, we now have centos8 workers added to the = autobuilder.
  • We are making various queued = changes to the autobuilder configuration to fix bugs, improve efficiency = and test coverage but this may result in some test result instability as = we test and resolve issues.
  • We’re collecting a list = of companies, products and projects which use the Yocto Project on the = wiki: https://wiki.yoctoproject.org/wiki/Project_Users<= /span> Please add any you know are missing (or email Richard/Stephen = who can add).
  • The triage team is worried = about attendance at triage meetings and the project is finding it hard = to find people to help fix bugs. If anyone is willing to work on bugs, = assistance would be greatly appreciated.

 

YP 3.1 Milestone = Dates:

  • YP 3.1 M3 build date = 2/24/2020
  • YP 3.1 M3 release date = 3/6/2020
  • YP 3.1 M4 build date  = 3/30/2020
  • YP 3.1 M4 release date  = 4/24/2020

 

Planned upcoming = dot releases:

  • YP 2.7.3 built and in = QA
  • YP 2.7.3 release date = 2/21/2020
  • YP 3.0.2 build date  = 2/3/2020
  • YP 3.0.2 release date = 2/14/2020

 

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_0B8B_01D5E632.C415E460--