+1 to release from the Intel side as well.
Sent: Wednesday, July 11, 2018 6:21 AM
To: Yeoh, Ee Peng <ee.peng.y...@intel.com>; 'firstname.lastname@example.org'
<email@example.com>; Jolley, Stephen K <stephen.k.jol...@intel.com>;
Eggleton, Paul <paul.eggle...@intel.com>
Cc: Sangal, Apoorv <apoorv.san...@intel.com>; Kirkiris, Nectar
Subject: Re: QA cycle report for 2.3.4 RC1
On Tue, 2018-07-10 at 06:11 +0000, Yeoh, Ee Peng wrote:
> This is the full report for 2.3.4.rc1:
> ======= Summary ========
> All planned tests were executed. There were zero high milestone
> defect. Team had found 3 new defects where yocto-bsp failed to create
> bootable image with new bsp layer , QEMU ended unexpectedly during
> do_testimage:core-image-lsb-sdk , & valgrind ptest passed in
> 2.3.3.rc1 failed at current release .
> ======= QA-Hints========
> Found 3 non critical defects.
> ======= Bugs ========
Thanks for this Ee Peng and team!
> New Bugs
>  Bug 12846 - [QA 2.3.4rc1][Meta-Yocto][Case 309, Case 310]: After
> creating BSP layer using yocto-bsp, the image created not able to boot
> up as local variable 'qbsys' referenced before assignment
Has this ever worked? I agree we should have a better error message but
ultimately its due to runqemu not understanding that MACHINE name.
I don't think that is a release blocker.
>  Bug 12812 - [2.3.4 rc1] Qemu ended unexpectedly during
We believe this is due to the infamous apic issues we've had with certain
kernel versions (IA only). Its annoying and something we should fix but not a
release blocker IMO.
>  Bug 12847 - [2.3.4 rc1] valgrind ptest failed
This is annoying but we'd probably focus on master for ptest work.
Looking at the various bugs filed against the release in the QA report, I think
there are some annoying issues but nothing to warrant an rc2 given our current
resource situation so I'd suggest releasing rc1.
yocto mailing list