From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Teoh, Jay Shen" <jay.shen.teoh@intel.com>,
"qa-build-notification@lists.yoctoproject.org"
<qa-build-notification@lists.yoctoproject.org>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.16.rc1)
Date: Fri, 29 Apr 2022 13:56:54 +0100 [thread overview]
Message-ID: <06250637d4cdd75a322e53dbe4a983c2488a2e3d.camel@linuxfoundation.org> (raw)
In-Reply-To: <DM5PR1101MB2348A19B6BC4935A96FE48A4BBFC9@DM5PR1101MB2348.namprd11.prod.outlook.com>
On Fri, 2022-04-29 at 05:32 +0000, Teoh, Jay Shen wrote:
> Hi All,
>
> This is the full report for yocto-3.1.16.rc1:
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
>
> ======= Summary ========
> No high milestone defects.
>
> No new issue found.
Thanks!
The TSC did discuss the perf issue earlier in the week and were good to release
if there were no other issues found, we should therefore be good to release.
Cheers,
Richard
prev parent reply other threads:[~2022-04-29 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0101018065844051-3f135aa2-6cb1-485c-aa27-2c921567884b-000000@us-west-2.amazonses.com>
2022-04-27 1:59 ` [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.16.rc1) Teoh, Jay Shen
[not found] ` <3c965c4de0252fed6b817deec761713addc6fb5d.camel@linuxfoundation.org>
2022-04-29 5:32 ` [yocto] " Teoh, Jay Shen
2022-04-29 12:56 ` Richard Purdie [this message]
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=06250637d4cdd75a322e53dbe4a983c2488a2e3d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jay.shen.teoh@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=qa-build-notification@lists.yoctoproject.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox