[yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc2)

[Jain, Sangeeta]

Hello All,

Intel and WR YP QA is now working on QA execution for YP build 2.8 M1 RC2.
We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:

1. OE-Core
2. BSP-hw
3. BSP-Qemu

Runtime auto test for following platforms:

1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. MPC8315e-rdb
7. Beaglebone

ETA for completion is Friday, 15 June.


Thanks & Regards,
Sangeeta Jain

>-----Original Message-----
>From: richard.purdie at linuxfoundation.org <richard.purdie at linuxfoundation.org>
>Sent: Tuesday, 11 June, 2019 4:51 PM
>To: pokybuild at debian9-ty-1.yocto.io; yocto at yoctoproject.org
>Cc: otavio at ossystems.com.br; yi.zhao at windriver.com; Sangal, Apoorv
><apoorv.sangal at intel.com>; Yeoh, Ee Peng <ee.peng.yeoh at intel.com>; Chan,
>Aaron Chun Yew <aaron.chun.yew.chan at intel.com>; Ang, Chin Huat
><chin.huat.ang at intel.com>; akuster808 at gmail.com; sjolley.yp.pm at gmail.com;
>Jain, Sangeeta <sangeeta.jain at intel.com>
>Subject: Re: QA notification for completed autobuilder build (yocto-2.8_M1.rc2)
>
>On Tue, 2019-06-11 at 03:32 +0000, pokybuild at debian9-ty-1.yocto.io
>wrote:
>> A build flagged for QA (yocto-2.8_M1.rc2) was completed on the
>> autobuilder and is available at:
>>
>>
>>     https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2
>>
>
>Some notes for QA:
>
>There was a failure in this build in qemux86 oe-selftest. It looks to be a race issue
>where qemu was shutting down. This needs a bug and looking into but is a minor
>issue which wouldn't block the milestone release or further QA.
>
>There are three timeouts in ptest, acl, bluez5 (#13366) and mdadm (#13368).
>These are also not going to block the milestone release. The
>bluez5 issue is gcc9 related, mdadm was exposed by wider testing in master. The
>acl issue needs a bug opening and investigation as that is a regression.
>
>There is a lot more testing happening under automation than in previous builds,
>particularly on arm hosts/targets.
>
>Cheers,
>
>Richard