From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW24
Date: Mon, 15 Jun 2020 15:45:17 -0700 [thread overview]
Message-ID: <173b01d64366$a46eac50$ed4c04f0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
All,
YP M+ or high bugs which moved to a new milestone in WW24 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
High
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13802> 13802
ltp tests fail with ssh connection lost error intermittently
randy.macleod@windriver.com
yang.wang@windriver.com
3.2 M1
3.2 M2
Medium+
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13411> 13411
ptest-perl.bbclass run-ptest is too greedy for SKIP
timothy.t.orling@intel.com
timothy.t.orling@intel.com
3.2
3.2 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13607> 13607
can't run bitbake on multiple multiconfig recipes
randy.macleod@windriver.com
richard.purdie@linuxfoundation.org
3.1 M3
3.2 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13897> 13897
POSTINST_INTERCEPTS_DIR broken by undocumented POSTINST_INTERCEPTS_PATHS
since thud
randy.macleod@windriver.com
mingli.yu@windriver.com
3.2 M1
3.2 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13909> 13909
Intermittent kernel reproducibility failure
randy.macleod@windriver.com
bruce.ashfield@gmail.com
3.2 M1
3.2 M2
Thanks,
Stephen K. Jolley
Yocto Project Program Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 16865 bytes --]
next reply other threads:[~2020-06-15 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 22:45 Stephen Jolley [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 0:24 M+ & H bugs with Milestone Movements WW24 Stephen Jolley
2022-06-14 14:21 sjolley.yp.pm
2023-06-20 0:42 sjolley.yp.pm
2025-06-17 3:37 Stephen K Jolley
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='173b01d64366$a46eac50$ed4c04f0$@gmail.com' \
--to=sjolley.yp.pm@gmail.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.