From: Saul Wold <sgw@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Yocto Project Status WW35
Date: Fri, 26 Aug 2016 10:29:36 -0700 [thread overview]
Message-ID: <1472232576.7558.51.camel@linux.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2343 bytes --]
Current Dev Position: YP 2.2 M3
Next Deadline: YP 2.2 M3 which will be Aug 29th (5:00pm GMT)
SWAT team rotation: Anibal -> Tracy
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
* The M3 deadline and feature freeze for 2.2 is on Monday. The patch queue is relatively low at the moment but it will likely take a few days to stablise and get all the patches merged. Beyond this point we will only be taking bugfixes for 2.2.
* The pre-M3 build we’ve run looks good from a QA perspective so far.
* We continue to see a significant ‘random’ autobuilder failures. Currently unknown/unresolved issues:
* Mips machine ‘failure to start’ despite booting the kernel: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10136
* Systemd logging failure: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10128
* Unknown ppc failure: https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/910/steps/Running%20Sanity%20Tests/logs/stdio
* gobject-introspection issues on mips-lsb and ppc-lsb from gstreamer1.0-plugins-bad
* Webkit gobject-introspection race over a file
These are all issue which potentially put the M3 and 2.2 final builds at risk
* We had a good performance gain on the autobuilders by enabling kvm, now our oldest supported distros support it reliably. This took runtime QA testing on x86 from around 45 minutes down to around 3 minutes which is a significant win, even if its x86 only.
* We have started testing musl world builds and also runtime x86 musl testing now the kvm change means the overhead is lower.
Key YP 2.2 Dates:
* YP 2.2 M1 release would be: 6/24/16
* YP 2.2 M2 cut off would be: 7/18/16
* YP 2.2 M2 release would be: 7/29/16
* YP 2.2 M3 cut off would be: 8/29/16
* YP 2.2 M3 release would be: 9/9/16
* YP 2.2 M4 cut off would be: 10/3/16
* YP 2.2 M4 release would be: 10/28/16
Tracking Metrics:
WDD 2747 (last week 2706)
(https://wiki.yoctoproject.org/charts/combo.html)
Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
[-- Attachment #2: Type: text/html, Size: 15293 bytes --]
next reply other threads:[~2016-08-26 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 17:29 Saul Wold [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-28 15:39 Yocto Project Status WW35 Jolley, Stephen K
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1472232576.7558.51.camel@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.