From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-f42.google.com (mail-pj1-f42.google.com [209.85.216.42]) by mail.openembedded.org (Postfix) with ESMTP id CC6827FAB6 for ; Tue, 14 Jan 2020 15:52:30 +0000 (UTC) Received: by mail-pj1-f42.google.com with SMTP id s7so6066951pjc.0 for ; Tue, 14 Jan 2020 07:52:32 -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:thread-index :content-language; bh=0VebnHunS+6L6gqYkJr8pQyCxCWSnmu4hUnsbHD0YLs=; b=LWrAKR5iD16+nYwKv/5yOOQh0XzA1adKetZ85LEXJTng2S4jikv1U/850/gb5cKcYa +63Fs3DyzlCquoRrSHRFd4h30vC8A0vim2h0J1nOfAwFKQYUUjE/7scT0ZOk8JgBuDje pn/9RpdIp64He+NYlrJCWVP+ecSPMLX4e5b0kw/2DNuIYZblL12+itC2q8eADXMF8sZQ P1TVUpmVzEbgvlYyn85bTep7s0eewV+oUBDyFRwmXUsvdabLJf56iD9gsFUGmGLVekHY JtyeF5hL6VDAb7GAVYBuGd3yj4yPM6lfK4ShOO2n7NXhFOKOGN20gvU35k+1XJYZu3U+ 5FAQ== 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 :thread-index:content-language; bh=0VebnHunS+6L6gqYkJr8pQyCxCWSnmu4hUnsbHD0YLs=; b=XLi/+M4WAfPs30hUOXeSndHczNicnZWKXal3i8UHTTEyeqQ2NYGZLS4DAlzwbEDQ5v f0HJfHge880khnIbkyneboNNsc2sFy5SnOwQ/Xa7K+sr4MptAd8lBtL8suuqtcYaWJ0L ZRQGF+dlIIggVNevzMppvkGMU3IPdhpMbH7A+UkQxPGdWLE+7SkcLq881V4eOXPNoVse sFepz+McPwYtPquUSd/EvpF3/3QSPGLzLHSvyXT7CEfpV9xaNpMFzXpPmTnEB5VhksQV CSa6/xDcgyWL/UrJqGgwQK20ctASe/rVRlKQimy+9vYgaCCOtq4nXUiwz7EvffvqDSdP 1BRA== X-Gm-Message-State: APjAAAWEfW2E5jPQMd8UBirPI0DcAybk+msfL6o21Lkwt68FmUmaRBSy Sw+s1d3o+uHj50AKHOn7jwY= X-Google-Smtp-Source: APXvYqxrwPsa0C7o76qreU979BOWtcHWbq1OSiefiIF5dzHtBh7vqAz36NJWpeOjdOhJ8CGFPDf9fA== X-Received: by 2002:a17:902:b08e:: with SMTP id p14mr13739885plr.323.1579017151805; Tue, 14 Jan 2020 07:52:31 -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 144sm19738595pfc.124.2020.01.14.07.52.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Jan 2020 07:52:31 -0800 (PST) From: To: , Date: Tue, 14 Jan 2020 07:52:31 -0800 Message-ID: <074801d5caf2$a160cdf0$e42269d0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdXK8nxl/vBWsfK0TI+o4V1ymOwJrA== Subject: Yocto Project Status WW03'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, 14 Jan 2020 15:52:30 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0749_01D5CAAF.933EED80" Content-Language: en-us ------=_NextPart_000_0749_01D5CAAF.933EED80 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M2 Next Deadline: YP 3.1 M2 build date 1/20/2020 Next Team Meetings: * Bug Triage meeting Thursday Jan. 16th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Feb. 4th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Jan. 14th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Jan. 14th at 8am PDT ( https://www.twitch.tv/yocto_project) Tip of the Week: * 'oe-pkgdata-browser' is a new handy small helper UI added by Ross to visualise the pkgdata held within a build. * (anyone with tips they'd like to see here, please send to Stephen or Richard) Key Status/Updates: * YP 3.1 M2 is due to be built next week. * Patch merging is roughly on track however there are a number of failures identified with key patches (glibc has a prelink issue on mips, python 3.8 upgrade blocked on uid issue, gstreamer meson transition blocked on nodistro failure). Most of these issues are making progress over time. * The more worrying aspect is that there are a number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage. * Looking at the build history, "full" images have built cleanly only once in the past month (3 times in the last two months), which is a pretty shocking statistic which summarises the challenges we face there. Most of these are being procrastinated on by the bug owners since we can't reproduce them at will. We really need help working on these kinds of issues. * We have changed the sstate mirrors to be per release, simply to lower the numbers of files in any given sstate directory. * 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 M2 build date 1/20/2020 * YP 3.1 M2 release date 1/31/2020 * 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 build date 2/10/2020 * 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 2772 (last week 2773) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1411 (last week 1400) * Patches in the Pending State: 562 (40%) [last week 562 (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 Project Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_0749_01D5CAAF.933EED80 Content-Type: text/html; boundary="----=_NextPart_000_184F_01D5C530.6F606CB0"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M2

Next Deadline: YP = 3.1 M2 build date 1/20/2020

 

Next Team = Meetings:

 

Tip of the = Week:

  • ‘oe-pkgdata-browser’= is a new handy small helper UI added by Ross to visualise the pkgdata = held within a build.
  • (anyone with tips they’d = like to see here, please send to Stephen or = Richard)

 

Key = Status/Updates:

  • YP 3.1 M2 is due to be built = next week.
  • Patch merging is roughly on = track however there are a number of failures identified with key patches = (glibc has a prelink issue on mips, python 3.8 upgrade blocked on uid = issue, gstreamer meson transition blocked on nodistro failure). Most of = these issues are making progress over time.
  • The more worrying aspect is = that there are a number of recurring/intermittent failures in the = automated testing, mostly from selftest and = testimage.
  • Looking at the build history, = “full” images have built cleanly only once in the past month = (3 times in the last two months), which is a pretty shocking statistic = which summarises the challenges we face there. Most of these are being = procrastinated on by the bug owners since we can’t reproduce them = at will. We really need help working on these kinds of = issues.
  • We have changed the sstate = mirrors to be per release, simply to lower the numbers of files in any = given sstate directory.
  • 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 M2 build date = 1/20/2020
  • YP 3.1 M2 release date = 1/31/2020
  • 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 build date  = 2/10/2020
  • 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 Project Manager

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

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

 

------=_NextPart_000_0749_01D5CAAF.933EED80-- 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.145.1579017155886673697 for ; Tue, 14 Jan 2020 07:52:36 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=LWrAKR5i; 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 7AE04E01380; Tue, 14 Jan 2020 07:52:35 -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.214.169 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-pl1-f169.google.com (mail-pl1-f169.google.com [209.85.214.169]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 48841E01309 for ; Tue, 14 Jan 2020 07:52:32 -0800 (PST) Received: by mail-pl1-f169.google.com with SMTP id f20so5393036plj.5 for ; Tue, 14 Jan 2020 07:52:32 -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:thread-index :content-language; bh=0VebnHunS+6L6gqYkJr8pQyCxCWSnmu4hUnsbHD0YLs=; b=LWrAKR5iD16+nYwKv/5yOOQh0XzA1adKetZ85LEXJTng2S4jikv1U/850/gb5cKcYa +63Fs3DyzlCquoRrSHRFd4h30vC8A0vim2h0J1nOfAwFKQYUUjE/7scT0ZOk8JgBuDje pn/9RpdIp64He+NYlrJCWVP+ecSPMLX4e5b0kw/2DNuIYZblL12+itC2q8eADXMF8sZQ P1TVUpmVzEbgvlYyn85bTep7s0eewV+oUBDyFRwmXUsvdabLJf56iD9gsFUGmGLVekHY JtyeF5hL6VDAb7GAVYBuGd3yj4yPM6lfK4ShOO2n7NXhFOKOGN20gvU35k+1XJYZu3U+ 5FAQ== 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 :thread-index:content-language; bh=0VebnHunS+6L6gqYkJr8pQyCxCWSnmu4hUnsbHD0YLs=; b=Q/oYVMYni97w2pTF1KlAiBj5vGxTVo2k7C5qErZ8Z3n9WMUnXUS+4As4XJW2uhbwfn L4Xpp+3GUw1QWdM175wiwU0sOuY7fD6I145Hh4SNLC3Sxf6N5Y2flkFzkbsLIsFx1PWi qLsTDzLtoU45TTRvJqU4p++CvoPK9MHOaWcsQoC2aY44GL/GWewi9coaiBaoE9tnYeLQ MXo6TyifLB30Uq6VPREoEYzJpC68u9BzIiloOJb8tS4z2CbcWTVUl8rWgugVatzAtMau nGf3vP9tIcspGyeQgBvS8Vr+46N4Fmc+39XRNJYwTcHAbLKL969Zrrq5FLQff+CpCVK1 bwfw== X-Gm-Message-State: APjAAAVnx6PBLYDb3hOOhHxRm7Cl4lh9H+kcr3ScufsQRNWDOBw+JgmX 1jmRLyZ6rwcG5qaswh9juiY= X-Google-Smtp-Source: APXvYqxrwPsa0C7o76qreU979BOWtcHWbq1OSiefiIF5dzHtBh7vqAz36NJWpeOjdOhJ8CGFPDf9fA== X-Received: by 2002:a17:902:b08e:: with SMTP id p14mr13739885plr.323.1579017151805; Tue, 14 Jan 2020 07:52:31 -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 144sm19738595pfc.124.2020.01.14.07.52.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Jan 2020 07:52:31 -0800 (PST) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW03'20 Date: Tue, 14 Jan 2020 07:52:31 -0800 Message-ID: <074801d5caf2$a160cdf0$e42269d0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdXK8nxl/vBWsfK0TI+o4V1ymOwJrA== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0749_01D5CAAF.933EED80" Content-Language: en-us ------=_NextPart_000_0749_01D5CAAF.933EED80 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M2 Next Deadline: YP 3.1 M2 build date 1/20/2020 Next Team Meetings: * Bug Triage meeting Thursday Jan. 16th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Feb. 4th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Jan. 14th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Jan. 14th at 8am PDT ( https://www.twitch.tv/yocto_project) Tip of the Week: * 'oe-pkgdata-browser' is a new handy small helper UI added by Ross to visualise the pkgdata held within a build. * (anyone with tips they'd like to see here, please send to Stephen or Richard) Key Status/Updates: * YP 3.1 M2 is due to be built next week. * Patch merging is roughly on track however there are a number of failures identified with key patches (glibc has a prelink issue on mips, python 3.8 upgrade blocked on uid issue, gstreamer meson transition blocked on nodistro failure). Most of these issues are making progress over time. * The more worrying aspect is that there are a number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage. * Looking at the build history, "full" images have built cleanly only once in the past month (3 times in the last two months), which is a pretty shocking statistic which summarises the challenges we face there. Most of these are being procrastinated on by the bug owners since we can't reproduce them at will. We really need help working on these kinds of issues. * We have changed the sstate mirrors to be per release, simply to lower the numbers of files in any given sstate directory. * 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 M2 build date 1/20/2020 * YP 3.1 M2 release date 1/31/2020 * 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 build date 2/10/2020 * 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 2772 (last week 2773) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1411 (last week 1400) * Patches in the Pending State: 562 (40%) [last week 562 (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 Project Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_0749_01D5CAAF.933EED80 Content-Type: text/html; boundary="----=_NextPart_000_184F_01D5C530.6F606CB0"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M2

Next Deadline: YP = 3.1 M2 build date 1/20/2020

 

Next Team = Meetings:

 

Tip of the = Week:

  • ‘oe-pkgdata-browser’= is a new handy small helper UI added by Ross to visualise the pkgdata = held within a build.
  • (anyone with tips they’d = like to see here, please send to Stephen or = Richard)

 

Key = Status/Updates:

  • YP 3.1 M2 is due to be built = next week.
  • Patch merging is roughly on = track however there are a number of failures identified with key patches = (glibc has a prelink issue on mips, python 3.8 upgrade blocked on uid = issue, gstreamer meson transition blocked on nodistro failure). Most of = these issues are making progress over time.
  • The more worrying aspect is = that there are a number of recurring/intermittent failures in the = automated testing, mostly from selftest and = testimage.
  • Looking at the build history, = “full” images have built cleanly only once in the past month = (3 times in the last two months), which is a pretty shocking statistic = which summarises the challenges we face there. Most of these are being = procrastinated on by the bug owners since we can’t reproduce them = at will. We really need help working on these kinds of = issues.
  • We have changed the sstate = mirrors to be per release, simply to lower the numbers of files in any = given sstate directory.
  • 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 M2 build date = 1/20/2020
  • YP 3.1 M2 release date = 1/31/2020
  • 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 build date  = 2/10/2020
  • 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 Project Manager

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

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

 

------=_NextPart_000_0749_01D5CAAF.933EED80--