From: "Sangeeta Jain" <sangeeta.jain@intel.com>
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Cc: "otavio@ossystems.com.br" <otavio@ossystems.com.br>,
"yi.zhao@windriver.com" <yi.zhao@windriver.com>,
"Sangal, Apoorv" <apoorv.sangal@intel.com>,
"Chan, Aaron Chun Yew" <aaron.chun.yew.chan@intel.com>,
"richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"akuster808@gmail.com" <akuster808@gmail.com>,
"sjolley.yp.pm@gmail.com" <sjolley.yp.pm@gmail.com>,
"Teoh, Jay Shen" <jay.shen.teoh@intel.com>
Subject: Re: [yocto] QA notification for completed autobuilder build (yocto-3.2.rc1)
Date: Wed, 21 Oct 2020 03:34:23 +0000 [thread overview]
Message-ID: <BYAPR11MB362449F8E07D7D67B5BA08F2E31C0@BYAPR11MB3624.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20201020163538.0C38244D07F@centos7-ty-4.yocto.io>
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.2.rc1
We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. Beaglebone
ETA for completion is next Monday, October 26.
Thanks,
Sangeeta
> -----Original Message-----
> From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf
> Of Pokybuild User
> Sent: Wednesday, 21 October, 2020 12:36 AM
> To: yocto@lists.yoctoproject.org
> Cc: otavio@ossystems.com.br; yi.zhao@windriver.com; Sangal, Apoorv
> <apoorv.sangal@intel.com>; Yeoh, Ee Peng <ee.peng.yeoh@intel.com>; Chan,
> Aaron Chun Yew <aaron.chun.yew.chan@intel.com>;
> richard.purdie@linuxfoundation.org; akuster808@gmail.com;
> sjolley.yp.pm@gmail.com; Jain, Sangeeta <sangeeta.jain@intel.com>
> Subject: [yocto] QA notification for completed autobuilder build (yocto-3.2.rc1)
>
>
> A build flagged for QA (yocto-3.2.rc1) was completed on the autobuilder and is
> available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-3.2.rc1
>
>
> Build hash information:
>
> bitbake: 9345d257ced432adc2d16af20ace58cc7c086aab
> meta-arm: b419151acd2761d0e2723f0d0c0bbbed00c45c5b
> meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43
> meta-intel: 0e4b3cb01735bdc5ebf50c547927f1f59b0248d2
> meta-kernel: dbf8bdfa6683404e5071feb47ef6aa347cab1b01
> meta-mingw: d2809d7c93bdb46014e1f8b3b0a4f42030078905
> oecore: ea8ba9a15bcec7f5fbce1f40170298f87a808249
> poky: 4e4a302e37ac06543e9983773cdb4caf7728330d
>
>
>
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.purdie@linuxfoundation.org
>
>
>
next prev parent reply other threads:[~2020-10-21 3:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 16:35 QA notification for completed autobuilder build (yocto-3.2.rc1) pokybuild
2020-10-21 3:34 ` Sangeeta Jain [this message]
2020-10-26 7:06 ` [yocto] " Sangeeta Jain
2020-10-26 22:36 ` Richard Purdie
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=BYAPR11MB362449F8E07D7D67B5BA08F2E31C0@BYAPR11MB3624.namprd11.prod.outlook.com \
--to=sangeeta.jain@intel.com \
--cc=aaron.chun.yew.chan@intel.com \
--cc=akuster808@gmail.com \
--cc=apoorv.sangal@intel.com \
--cc=jay.shen.teoh@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=richard.purdie@linuxfoundation.org \
--cc=sjolley.yp.pm@gmail.com \
--cc=yi.zhao@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.