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

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

[Pokybuild User]

A build flagged for QA (yocto-2.6.3.rc1) was completed on the autobuilder and is available at:


    https://autobuilder.yocto.io/pub/releases/yocto-2.6.3.rc1


Build hash information: 

bitbake: 4ce92f43eeac6a4bfd06e8567fa6891614b5b3b0
meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575
meta-intel: 278f0b5fa2f1836635178bdc770e035d77ae03c7
meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5
oecore: d3d3f443039b03f1200a14bfe99f985592632018
poky: cb26830f765f03309c0663352cc5849491271be8



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@linuxfoundation.org


 

Re: QA notification for completed autobuilder build (yocto-2.6.3.rc1)

[Yeoh, Ee Peng]

Hello All,

Intel and WR YP QA is planning for QA execution for YP build yocto-2.6.3.rc1.
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. NUC 7
3. NUC 6
4. Edgerouter
5. MPC8315e-rdb
6. Beaglebone

ETA for completion is next Wednesday, August 07.

-----Original Message-----
From: Pokybuild User [mailto:pokybuild@debian10-ty-3.yocto.io] 
Sent: Thursday, August 1, 2019 11:04 PM
To: yocto@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>; Ang, Chin Huat <chin.huat.ang@intel.com>; richard.purdie@linuxfoundation.org; akuster808@gmail.com; sjolley.yp.pm@gmail.com; Jain, Sangeeta <sangeeta.jain@intel.com>
Subject: QA notification for completed autobuilder build (yocto-2.6.3.rc1)


A build flagged for QA (yocto-2.6.3.rc1) was completed on the autobuilder and is available at:


    https://autobuilder.yocto.io/pub/releases/yocto-2.6.3.rc1


Build hash information: 

bitbake: 4ce92f43eeac6a4bfd06e8567fa6891614b5b3b0
meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575
meta-intel: 278f0b5fa2f1836635178bdc770e035d77ae03c7
meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5
oecore: d3d3f443039b03f1200a14bfe99f985592632018
poky: cb26830f765f03309c0663352cc5849491271be8



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@linuxfoundation.org


 

Re: QA notification for completed autobuilder build (yocto-2.6.3.rc1)

[Jain, Sangeeta]

Hello All,

This is the full report for 2.6.3 RC1:  
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.  
No new defects are found in this build.

=======QA notes=========
One minor issue is observed, after installed core-image-sato-sdk image to NUC7 internal harddisk, during boot up, it hangs at the Yocto splash screen. Need to manual press keyboard "enter" button multiple times for it to continue the boot and bring the screen to sato GUI. No bug is filed for this issue as this seems to be a minor issue and QA team investigating more onto it. This bug is consistently reproducible.


Thanks & Regards,
Sangeeta Jain

Re: QA notification for completed autobuilder build (yocto-2.6.3.rc1)

[richard.purdie]

On Thu, 2019-08-08 at 03:00 +0000, Jain, Sangeeta wrote:
> Hello All,
> 
> This is the full report for 2.6.3 RC1:  
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults
> 
> ======= Summary ========
> No high milestone defects.  
> No new defects are found in this build.
> 
> =======QA notes=========
> One minor issue is observed, after installed core-image-sato-sdk
> image to NUC7 internal harddisk, during boot up, it hangs at the
> Yocto splash screen. Need to manual press keyboard "enter" button
> multiple times for it to continue the boot and bring the screen to
> sato GUI. No bug is filed for this issue as this seems to be a minor
> issue and QA team investigating more onto it. This bug is
> consistently reproducible.

Thanks for running the tests.

FWIW the issue above sounds very like a lack of entropy problem, you
may want to look at the kernel configuration and see how its generating
entropy. If you can see the kernel boot messages and disable the splash
screen that would help debug it.

Cheers,

Richard

Re: QA notification for completed autobuilder build (yocto-2.6.3.rc1)

[Jain, Sangeeta]

>-----Original Message-----
>From: richard.purdie@linuxfoundation.org <richard.purdie@linuxfoundation.org>
>Sent: Thursday, 8 August, 2019 4:29 PM
>To: Jain, Sangeeta <sangeeta.jain@intel.com>; yocto@yoctoproject.org
>Cc: otavio@ossystems.com.br; yi.zhao@windriver.com; Sangal, Apoorv
><apoorv.sangal@intel.com>; Chan, Aaron Chun Yew
><aaron.chun.yew.chan@intel.com>; Ang, Chin Huat <chin.huat.ang@intel.com>;
>akuster808@gmail.com; sjolley.yp.pm@gmail.com; Yeoh, Ee Peng
><ee.peng.yeoh@intel.com>; Tummalapalli, Vineela
><vineela.tummalapalli@intel.com>
>Subject: Re: QA notification for completed autobuilder build (yocto-2.6.3.rc1)
>
>On Thu, 2019-08-08 at 03:00 +0000, Jain, Sangeeta wrote:
>> Hello All,
>>
>> This is the full report for 2.6.3 RC1:
>> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/l
>> og/?h=intel-yocto-testresults
>>
>> ======= Summary ========
>> No high milestone defects.
>> No new defects are found in this build.
>>
>> =======QA notes=========
>> One minor issue is observed, after installed core-image-sato-sdk image
>> to NUC7 internal harddisk, during boot up, it hangs at the Yocto
>> splash screen. Need to manual press keyboard "enter" button multiple
>> times for it to continue the boot and bring the screen to sato GUI. No
>> bug is filed for this issue as this seems to be a minor issue and QA
>> team investigating more onto it. This bug is consistently
>> reproducible.
>
>Thanks for running the tests.
>
>FWIW the issue above sounds very like a lack of entropy problem, you may want
>to look at the kernel configuration and see how its generating entropy. If you can
>see the kernel boot messages and disable the splash screen that would help
>debug it.

Thanks for the pointer Richard. It will help in debugging.
>
>Cheers,
>
>Richard

Thanks,
Sangeeta