From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2D450C4332F for ; Tue, 5 Oct 2021 15:11:02 +0000 (UTC) Received: from mail-pj1-f47.google.com (mail-pj1-f47.google.com [209.85.216.47]) by mx.groups.io with SMTP id smtpd.web11.1960.1633446660811098655 for ; Tue, 05 Oct 2021 08:11:00 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=KR/vnmv+; spf=pass (domain: gmail.com, ip: 209.85.216.47, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pj1-f47.google.com with SMTP id np13so4367138pjb.4 for ; Tue, 05 Oct 2021 08:11:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:subject:date:message-id:mime-version:thread-index :content-language; bh=Y3pctMQG89Y6W5LAiGrM/7FUT+/g4ZQwEX+q5iFtfV8=; b=KR/vnmv++796GeF9LORud8NZ1cXOdJrXt2QgR9RxlCg50O2BwXHAZf5uAwPRAmeNLg SaCIVDDkh6tei7VZ2HoCrawnRfy2XRaFCErWiuzyEbf48gcbDyaSgq3tDHHJvrdcVZL4 MuHt9S+cHvzNUTupHFCpMS68e9TMmiP439IZJkbC3z2zPZOEUlb5jQCTy2z/5VVIfRTV T6CfwrACW4zCgknFx3gY9Hc/n+QEBQgDc5JlrP3cY75/D+BuZRqgNn7QCOG6aY1rsSrx oMHkxIQfNBUk2yxhdquiYSy/2pxUI5tpCLMJyxKIIIkWgJ1o5u7DTM/niwIZhp8xB4L8 vT2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :thread-index:content-language; bh=Y3pctMQG89Y6W5LAiGrM/7FUT+/g4ZQwEX+q5iFtfV8=; b=qQe8nAtJ12RCiUBDOojG2oWvsaqE4p1hJLhabE8D5GLBDaA+0R4dFGvYLZbTTPMkNc DJIYrbY+w9avq+LweC9psSZVcNXdIXYHuUGfQNc7C6C2fRanSsARtE+zCi65/fqxXCPI yBVSYIsq2PfCUi4V1Q2g7ovCGH3JO7KPUlVeIWgFqx/+ZTtK3WbeOuE+6OlImVEJVQKU HzEyd5yMTKjqwI96HZ62X+xHltBX9cdcMtijf0XOiqgk2SxiXxbnfLL/ZuJ812HwJrOV 499nDSojQXITv4wY+shY959QyraE+MOMW5jVY4Ug07fZmRCkldbThGMf8+1CsICzewwi EmDQ== X-Gm-Message-State: AOAM533G+OrhMdjrq3RC+FTLGGPWYBecNY3aptoXDfGufd3CAFo6DuId WLS/vyTOVIlJ9RG/LpNbuFJAJ6bMoRY= X-Google-Smtp-Source: ABdhPJwZMLAKIWyD0twmmhU8eD9BUrlfLiDVI6w+wfBSlvX5JIu7oAbevh5zb4sVhTP0VOqhLxnrLw== X-Received: by 2002:a17:902:64d6:b0:13e:a59e:332c with SMTP id y22-20020a17090264d600b0013ea59e332cmr5643046pli.30.1633446659909; Tue, 05 Oct 2021 08:10:59 -0700 (PDT) Received: from skjolley ([2600:8800:1d92:f800:9c3b:4c8e:41b8:3847]) by smtp.gmail.com with ESMTPSA id q6sm11123768pfn.199.2021.10.05.08.10.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Oct 2021 08:10:59 -0700 (PDT) From: To: , Subject: Yocto Project Status WW40`21 Date: Tue, 5 Oct 2021 08:10:58 -0700 Message-ID: <0d5501d7b9fb$343494b0$9c9dbe10$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0D56_01D7B9C0.87D87BD0" X-Mailer: Microsoft Outlook 16.0 Thread-Index: Ade5+xsMD9JNNovNR0mBfDKrlFOknQ== Content-Language: en-us List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Tue, 05 Oct 2021 15:11:02 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/156649 This is a multipart message in MIME format. ------=_NextPart_000_0D56_01D7B9C0.87D87BD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.4 M4 Next Deadline: 4th Oct. 2021 YP 3.4 M4 build Next Team Meetings: * Bug Triage meeting Thursday Oct. 7th at 7:30am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) * Monthly Project Meeting Tuesday Oct. 5th at 8am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 ) * Weekly Engineering Sync Tuesday Oct. 12th at 8am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 ) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * The final 3.4 build is now due. * We should be in a reasonable position and ready for the 3.4 build, except for the SOURCE_DATE_EPOCH corruption issues we're seeing. Once those issues and the related sstate reuse issues are fixed, we'll build 3.4. At this point there are other patches but they're causing failures and clearly aren't ready for merging. * There continues to be an sstate reuse issue where native sstate on aarch64 and x86_64 hosts isn't generating correct hashes when combined with hash equivalence. * Intermittent issues took a significant rise last week as SWAT caught up with the backlog of issues. Help is very much welcome on these issues. 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 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.4. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.4_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.4 Milestone Dates: * YP 3.4 M4 build date 2021/10/04 * YP 3.4 M4 Release date 2021/10/29 Tracking Metrics: * WDD 2671 (last week 2676) ( https://wiki.yoctoproject.org/charts/combo.html) * OE-Core/Poky Patch Metrics * Total patches found: 1318 (last week 1309) * Patches in the Pending State: 488 (37%) [last week 484 (37%)] 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_0D56_01D7B9C0.87D87BD0 Content-Type: text/html; boundary="----=_NextPart_000_02E2_01D7B461.98150220"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.4 M4

Next Deadline: 4th = Oct. 2021 YP 3.4 M4 build

 

Next Team = Meetings:

 

Key = Status/Updates:

  • The final 3.4 build is now = due.
  • We should be in a reasonable = position and ready for the 3.4 build, except for the SOURCE_DATE_EPOCH = corruption issues we’re seeing. Once those issues and the related = sstate reuse issues are fixed, we’ll build 3.4. At this point = there are other patches but they’re causing failures and clearly = aren’t ready for merging.
  • There continues to be an sstate = reuse issue where native sstate on aarch64 and x86_64 hosts isn’t = generating correct hashes when combined with hash = equivalence.
  • Intermittent issues took a = significant rise last week as SWAT caught up with the backlog of issues. = Help is very much welcome on these issues. 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

 

Ways to = contribute:

 

YP 3.4 Milestone = Dates:

  • YP 3.4 M4 build date = 2021/10/04
  • YP 3.4 M4 Release date = 2021/10/29

 

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_0D56_01D7B9C0.87D87BD0--