All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW11
Date: Mon, 16 Mar 2020 09:50:45 -0700	[thread overview]
Message-ID: <03a901d5fbb3$0a3dd5c0$1eb98140$@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

All,

YP M+ or high bugs which moved to a new milestone in WW11 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


High

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=13604> 13604

[master-next] Distrodata.test_maintainers  fails

randy.macleod@windriver.com

kai.kang@windriver.com

3.1 M3

3.1 M4


 

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=13714> 13714

add gcc to buildtools for Centos7 uninative

randy.macleod@windriver.com

timothy.t.orling@intel.com

3.1 M3

3.1 M4


 

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=13802> 13802

ltp tests fail with ssh connection lost  error intermittently

richard.purdie@linuxfoundation.org

akuster@mvista.com

3.1 M3

3.1 M4


Medium+

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=12604> 12604

Default ptest-runner invocation on multilib may not execute any test suites

randy.macleod@windriver.com

limon.anibal@gmail.com

3.99

3.2

 

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: 14650 bytes --]

             reply	other threads:[~2020-03-16 16:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 16:50 Stephen Jolley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-15 19:15 M+ & H bugs with Milestone Movements WW11 Stephen Jolley
2022-03-14 23:16 sjolley.yp.pm
2023-03-20 21:55 sjolley.yp.pm
2024-03-18 23:57 Stephen K Jolley
2026-03-17  5:32 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='03a901d5fbb3$0a3dd5c0$1eb98140$@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.