QA notification for completed autobuilder build (yocto-3.2.rc1)

QA notification for completed autobuilder build (yocto-3.2.rc1)

[pokybuild]

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


 

Re: [yocto] QA notification for completed autobuilder build (yocto-3.2.rc1)

[Sangeeta Jain]

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
> 
> 
> 

Re: [yocto] QA notification for completed autobuilder build (yocto-3.2.rc1)

[Sangeeta Jain]

Hello all,

This is the full report for yocto-3.2.rc1:  
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No new defects are found.
No high milestone defects.

glib-2.0 ptest failed (BUG id:14106)
  
Bugs verified:

BUG id:14050 - [QA 3.2 M3 RC1] failure in ptest : parted component
   Verified Fixed.

Existing bugs observed in this release:

valgrind ptest failed (BUG id:14051)
   Updated with 2 ptests passed and 3 new failures.
  
======= Bugs ========
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14106
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14050
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14051

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
> 
> 
> 

Re: [yocto] QA notification for completed autobuilder build (yocto-3.2.rc1)

[Richard Purdie]

On Mon, 2020-10-26 at 07:06 +0000, Jain, Sangeeta wrote:
> Hello all,
> 
> This is the full report for yocto-3.2.rc1:  
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
> 
> ======= Summary ========
> No new defects are found.
> No high milestone defects.
> 
> glib-2.0 ptest failed (BUG id:14106)
>   
> Bugs verified:
> 
> BUG id:14050 - [QA 3.2 M3 RC1] failure in ptest : parted component
>    Verified Fixed.
> 
> Existing bugs observed in this release:
> 
> valgrind ptest failed (BUG id:14051)
>    Updated with 2 ptests passed and 3 new failures.
>   
> ======= Bugs ========
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14106
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14050
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=14051

Thanks for this Sangeeta and team!

Since this is final 3.2 we're keen to ensure we sort out the issues we
can. There was a buildhistory issue that became apparent in the last
few days. Adding in the above two ptest issues and we probably can't
release rc1.

I've merged fixes for the buildhistory issue and both the glib-2.0 and
valgrind ptest issues along with some other small tweaks and have
triggered a build of rc2.

Cheers,

Richard