From: "Trevor Gamblin" <trevor.gamblin@windriver.com>
To: Yocto-mailing-list <yocto@lists.yoctoproject.org>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
trevor.gamblin@windriver.com, "MacLeod,
Randy" <Randy.MacLeod@windriver.com>,
steve@sakoman.com, Tony Tascioglu <tony.tascioglu@windriver.com>,
"jpewhacker@gmail.com" <jpewhacker@gmail.com>,
"timothy.t.orling@intel.com" <timothy.t.orling@intel.com>,
Michael Opdenacker <michael.opdenacker@bootlin.com>,
"sjolley.yp.pm@gmail.com" <sjolley.yp.pm@gmail.com>
Subject: Minutes: Yocto Project Weekly Triage Meeting 7/29/2021
Date: Thu, 29 Jul 2021 11:13:52 -0400 [thread overview]
Message-ID: <6f994685-4b63-8ed2-8941-441909e3e0e6@windriver.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage
*Attendees:* Diane, Joshua, MichaelO, Randy, Richard, Stephen, Steve,
Tim, Tony, TrevorG
*ARs:*
- Tim to talk with Intel team about bug 14491 ([QA 3.4_M2.rc1] -
stap.StapTest.test_stap failure)
- Randy to discuss bug (save which recipe fetches which source) with
Robert and come to a conclusion
*Notes:*
*
*
- Steve encountered build failures such as the one in
https://errors.yoctoproject.org/Errors/Details/593109/ when attempting
to run dunfell builds with the PARALLEL_MAKE load averaging added. WR is
testing/investigating on internal Autobuilder instance
*Medium+ 3.4 Unassigned Enhancements/Bugs: *80 (Last week 73)
*Medium+ 3.99 Unassigned Enhancements/Bugs: *28**(Last week 27)
*AB-INT Bugs: *46 (Last week 49)
[-- Attachment #2: Type: text/html, Size: 2036 bytes --]
reply other threads:[~2021-07-29 15:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6f994685-4b63-8ed2-8941-441909e3e0e6@windriver.com \
--to=trevor.gamblin@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=jpewhacker@gmail.com \
--cc=michael.opdenacker@bootlin.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=sjolley.yp.pm@gmail.com \
--cc=steve@sakoman.com \
--cc=timothy.t.orling@intel.com \
--cc=tony.tascioglu@windriver.com \
--cc=yocto@lists.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.