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

[Jain, Sangeeta]

Hello all,

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

=== Summary 
No high milestone defects.  
No new defect found in this cycle.


Thanks & Regards,
Sangeeta Jain

>-Original Message-
>From: Pokybuild User 
>Sent: Thursday, October 31, 2019 1:23 AM
>To: yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; richard.pur...@linuxfoundation.org;
>akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, Sangeeta
>
>Subject: QA notification for completed autobuilder build (yocto-2.7.2.rc1)
>
>
>A build flagged for QA (yocto-2.7.2.rc1) was completed on the autobuilder and 
>is
>available at:
>
>
>https://autobuilder.yocto.io/pub/releases/yocto-2.7.2.rc1
>
>
>Build hash information:
>
>bitbake: 75d6648f232a06b99c54a1e33324a7fc1cd15b38
>meta-gplv2: d5d9fc9a4bbd365d6cd6fe4d6a8558f7115c17da
>meta-intel: ca26bed652722167b2dbe0042cfc2406029e9c6c
>meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4
>oecore: 726c3b92298981f5aa2f2449ceeec7b4bf84ed29
>poky: d0f73121551dc98f6924cd77952bf9ebf5ef3dd7
>
>
>
>This is an automated message from the Yocto Project Autobuilder
>Git: git://git.yoctoproject.org/yocto-autobuilder2
>Email: richard.pur...@linuxfoundation.org
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Jain, Sangeeta]

Hello All,

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

ETA for completion is Monday, November 18.

Thanks & Regards,
Sangeeta Jain
>-Original Message-
>From: Pokybuild User 
>Sent: Thursday, October 31, 2019 1:23 AM
>To: yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; richard.pur...@linuxfoundation.org;
>akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, Sangeeta
>
>Subject: QA notification for completed autobuilder build (yocto-2.7.2.rc1)
>
>
>A build flagged for QA (yocto-2.7.2.rc1) was completed on the autobuilder and 
>is
>available at:
>
>
>https://autobuilder.yocto.io/pub/releases/yocto-2.7.2.rc1
>
>
>Build hash information:
>
>bitbake: 75d6648f232a06b99c54a1e33324a7fc1cd15b38
>meta-gplv2: d5d9fc9a4bbd365d6cd6fe4d6a8558f7115c17da
>meta-intel: ca26bed652722167b2dbe0042cfc2406029e9c6c
>meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4
>oecore: 726c3b92298981f5aa2f2449ceeec7b4bf84ed29
>poky: d0f73121551dc98f6924cd77952bf9ebf5ef3dd7
>
>
>
>This is an automated message from the Yocto Project Autobuilder
>Git: git://git.yoctoproject.org/yocto-autobuilder2
>Email: richard.pur...@linuxfoundation.org
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)

[Jain, Sangeeta]

Hello all,

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

=== Summary 
No high milestone defects.  
No new defect found in this cycle.
The stap test case failure on beaglebone still exists in this release (BUG 
id:13273). 

=== Bugs 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13273

Thanks & Regards,
Sangeeta Jain

>-Original Message-
>From: Poky Build User 
>Sent: Friday, October 18, 2019 5:18 AM
>To: yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; richard.pur...@linuxfoundation.org;
>akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, Sangeeta
>
>Subject: QA notification for completed autobuilder build (yocto-2.6.4.rc2)
>
>
>A build flagged for QA (yocto-2.6.4.rc2) was completed on the autobuilder and 
>is
>available at:
>
>
>https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc2
>
>
>Build hash information:
>
>bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb
>meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575
>meta-intel: c200851435f39acd2fe4abbf7a05fbf617833964
>meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5
>oecore: cd7cf933b3235560ec71576d8f3836dff736a39f
>poky: 51f6145f8f99a02df1dad937684f014b0172e72a
>
>
>
>This is an automated message from the Yocto Project Autobuilder
>Git: git://git.yoctoproject.org/yocto-autobuilder2
>Email: richard.pur...@linuxfoundation.org
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)

[Jain, Sangeeta]

Hello All,

Intel and WR YP QA is planning for QA execution for YP build yocto-2.6.4.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 next Wednesday, October 23.


Thanks & Regards,
Sangeeta Jain

>-Original Message-
>From: Yeoh, Ee Peng 
>Sent: Friday, 18 October, 2019 9:05 AM
>To: Jain, Sangeeta 
>Subject: FW: QA notification for completed autobuilder build (yocto-2.6.4.rc2)
>
>FYI
>
>-Original Message-
>From: Poky Build User 
>Sent: Friday, October 18, 2019 5:18 AM
>To: yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; richard.pur...@linuxfoundation.org;
>akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, Sangeeta
>
>Subject: QA notification for completed autobuilder build (yocto-2.6.4.rc2)
>
>
>A build flagged for QA (yocto-2.6.4.rc2) was completed on the autobuilder and 
>is
>available at:
>
>
>https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc2
>
>
>Build hash information:
>
>bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb
>meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575
>meta-intel: c200851435f39acd2fe4abbf7a05fbf617833964
>meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5
>oecore: cd7cf933b3235560ec71576d8f3836dff736a39f
>poky: 51f6145f8f99a02df1dad937684f014b0172e72a
>
>
>
>This is an automated message from the Yocto Project Autobuilder
>Git: git://git.yoctoproject.org/yocto-autobuilder2
>Email: richard.pur...@linuxfoundation.org
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)

[Jain, Sangeeta]

>-Original Message-
>From: yocto-boun...@yoctoproject.org  On
>Behalf Of akuster
>Sent: Friday, 18 October, 2019 6:53 AM
>To: yocto@yoctoproject.org
>Cc: akuster...@gmail.com; Chan, Aaron Chun Yew
>; ota...@ossystems.com.br
>Subject: Re: [yocto] QA notification for completed autobuilder build (yocto-
>2.6.4.rc2)
>
>Can we get 2.6.4-rc2 in a QA queue for the next dot release?

Do you mean that we should wait for 2.7.2 before starting QA for 2.6.4-rc2?
>
>- armin
>

Thanks & Regards,
Sangeeta Jain

>On 10/17/19 2:17 PM, Poky Build User wrote:
>> A build flagged for QA (yocto-2.6.4.rc2) was completed on the autobuilder and
>is available at:
>>
>>
>> https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc2
>>
>>
>> Build hash information:
>>
>> bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb
>> meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575
>> meta-intel: c200851435f39acd2fe4abbf7a05fbf617833964
>> meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5
>> oecore: cd7cf933b3235560ec71576d8f3836dff736a39f
>> poky: 51f6145f8f99a02df1dad937684f014b0172e72a
>>
>>
>>
>> This is an automated message from the Yocto Project Autobuilder
>> Git: git://git.yoctoproject.org/yocto-autobuilder2
>> Email: richard.pur...@linuxfoundation.org
>>
>>
>>
>
>--
>___
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Yocto] QA cycle report for yocto-3.0_rc2

[Jain, Sangeeta]

Hello all,

This is the full QA report for YP 3.0 RC2:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/3.0_RC2?h=intel-yocto-testresults

=== Summary 
No high milestone defects.
Two new defects are found in this cycle, mpc8315e-rdb: the stap oeqa test 
causes OOM (BUG id:13594)
and strace ptest failed (BUG id:13595).

Verified (BUG id: 13555)


=== Bugs 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13595
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13594

Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-3.0.rc2)

[Jain, Sangeeta]

Hello All,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.0.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 next Tuesday, October 15.


Thanks & Regards,
Sangeeta Jain


>-Original Message-
>From: pokybu...@fedora30-ty-2.yocto.io 
>Sent: Thursday, October 10, 2019 12:11 PM
>To: yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; richard.pur...@linuxfoundation.org;
>akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, Sangeeta
>
>Subject: QA notification for completed autobuilder build (yocto-3.0.rc2)
>
>
>A build flagged for QA (yocto-3.0.rc2) was completed on the autobuilder and is
>available at:
>
>
>https://autobuilder.yocto.io/pub/releases/yocto-3.0.rc2
>
>
>Build hash information:
>
>bitbake: 5d83d828cacb58ccb7c464e799c85fd2d2a50ccc
>meta-gplv2: 9ca96786fd851150b518388bcb166efa0b4dfff9
>meta-intel: 13fcf624491cdd0d9b3eb78a4f0cd1781b482b51
>meta-mingw: 756963cc28ebc163df7d7f4b4ee004c18d3d3260
>oecore: 59938780e7e776d87146002ea939b185f8704408
>poky: 94f6b31befda5c496f65e863a6f8152b42d7ebf0
>
>
>
>This is an automated message from the Yocto Project Autobuilder
>Git: git://git.yoctoproject.org/yocto-autobuilder2
>Email: richard.pur...@linuxfoundation.org
>
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA cycle report for 2.8 M3 RC1

[Jain, Sangeeta]

Hello All,

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

=== Summary 
No high milestone defects.
Two new defects are found in this cycle, mpc8315e-rdb System randomly hang when 
running commands (BUG id:13555)
Due to this issue, oeqa would be timeout and many tests are skipped/failed on 
mpc8315e-rdb.
and ptest failed (BUG id:13556).

=== Bugs 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13555
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13556

Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Jain, Sangeeta]

>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Monday, 23 September, 2019 3:46 PM
>To: Jain, Sangeeta ; yocto@yoctoproject.org;
>Tummalapalli, Vineela 
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; akuster...@gmail.com; sjolley.yp...@gmail.com
>Subject: Re: QA notification for completed autobuilder build (yocto-2.8_M3.rc1)
>
>On Mon, 2019-09-23 at 07:37 +, Jain, Sangeeta wrote:
>> Hi Richard,
>>
>> LSB support was expected to be removed from build 'yocto-2.8_M3.rc1'
>> onwards, but link on AB still points to LSB images.
>> The images present inside
>> https://autobuilder.yocto.io/pub/releases/yocto-
>2.8_M3.rc1/machines/genericx86-64-lsb/
>>   are built with systemd as init manager.
>>
>> Can you please confirm if these are altcfg images and the link name
>> needs to updated?
>
>Well spotted!
>
>I can confirm these are altcfg images which have systemd as the init manager.
>
>For backwards compatibility the autobuilder target names didn't change but the
>configuration they're built with did. I hadn't realised this would be visible 
>in the
>release so we may need to think about that for
>M4 but they are altcfg images.
>

Thanks for confirmation. We will include them in test coverage.
>[Added Vineela to cc:]
>
>Cheers,
>
>Richard

Thanks,
Sangeeta

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Jain, Sangeeta]

Hi Richard,

LSB support was expected to be removed from build 'yocto-2.8_M3.rc1' onwards, 
but link on AB still points to LSB images.
The images present inside 
https://autobuilder.yocto.io/pub/releases/yocto-2.8_M3.rc1/machines/genericx86-64-lsb/
  are built with systemd as init manager.

Can you please confirm if these are altcfg images and the link name needs to 
updated?

Thanks,
Sangeeta Jain

>-Original Message-
>From: Jain, Sangeeta
>Sent: Monday, 23 September, 2019 11:09 AM
>To: pokybu...@ubuntu1804-ty-1.yocto.io; yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; richard.pur...@linuxfoundation.org;
>akuster...@gmail.com; sjolley.yp...@gmail.com; Tummalapalli, Vineela
>
>Subject: RE: QA notification for completed autobuilder build (yocto-2.8_M3.rc1)
>
>Hello All,
>
>Intel and WR YP QA is planning for QA execution for YP build yocto-2.8_M3.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. Coffee Lake
>3. NUC 7
>4. NUC 6
>5. Edgerouter
>6. MPC8315e-rdb
>7. Beaglebone
>
>ETA for completion is next Thursday, September 26.
>
>Thanks & Regards,
>Sangeeta Jain
>
>>-Original Message-
>>From: pokybu...@ubuntu1804-ty-1.yocto.io
>>[mailto:pokybuild@ubuntu1804-ty- 1.yocto.io]
>>Sent: Friday, September 20, 2019 1:01 PM
>>To: yocto@yoctoproject.org
>>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>>; Yeoh, Ee Peng ;
>>Chan, Aaron Chun Yew ; Ang, Chin Huat
>>; richard.pur...@linuxfoundation.org;
>>akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, Sangeeta
>>
>>Subject: QA notification for completed autobuilder build
>>(yocto-2.8_M3.rc1)
>>
>>
>>A build flagged for QA (yocto-2.8_M3.rc1) was completed on the
>>autobuilder and is available at:
>>
>>
>>https://autobuilder.yocto.io/pub/releases/yocto-2.8_M3.rc1
>>
>>
>>Build hash information:
>>
>>bitbake: 797354d285f6d624d9adb52bab65823572da0e39
>>meta-gplv2: 1e2480e50f34e55bdfd5e06f98441e03a3752d5a
>>meta-intel: 655dfaec95196b9c0e15d34f490e4a51a7d501e3
>>meta-mingw: 9df4e115ab9a7ab23f81fdbcc62b2a0269d6377f
>>oecore: 95ad5626296380358c8a502a3e04879dab653d78
>>poky: 81f9e815d36848761a9dfa94b00ad998bb39a4a6
>>
>>
>>
>>This is an automated message from the Yocto Project Autobuilder
>>Git: git://git.yoctoproject.org/yocto-autobuilder2
>>Email: richard.pur...@linuxfoundation.org
>>
>>
>>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Jain, Sangeeta]

Hello All,

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

ETA for completion is next Thursday, September 26.

Thanks & Regards,
Sangeeta Jain

>-Original Message-
>From: pokybu...@ubuntu1804-ty-1.yocto.io [mailto:pokybuild@ubuntu1804-ty-
>1.yocto.io]
>Sent: Friday, September 20, 2019 1:01 PM
>To: yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; richard.pur...@linuxfoundation.org;
>akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, Sangeeta
>
>Subject: QA notification for completed autobuilder build (yocto-2.8_M3.rc1)
>
>
>A build flagged for QA (yocto-2.8_M3.rc1) was completed on the autobuilder and
>is available at:
>
>
>https://autobuilder.yocto.io/pub/releases/yocto-2.8_M3.rc1
>
>
>Build hash information:
>
>bitbake: 797354d285f6d624d9adb52bab65823572da0e39
>meta-gplv2: 1e2480e50f34e55bdfd5e06f98441e03a3752d5a
>meta-intel: 655dfaec95196b9c0e15d34f490e4a51a7d501e3
>meta-mingw: 9df4e115ab9a7ab23f81fdbcc62b2a0269d6377f
>oecore: 95ad5626296380358c8a502a3e04879dab653d78
>poky: 81f9e815d36848761a9dfa94b00ad998bb39a4a6
>
>
>
>This is an automated message from the Yocto Project Autobuilder
>Git: git://git.yoctoproject.org/yocto-autobuilder2
>Email: richard.pur...@linuxfoundation.org
>
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Jain, Sangeeta]

>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Thursday, 8 August, 2019 4:29 PM
>To: Jain, Sangeeta ; yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Chan, Aaron Chun Yew
>; Ang, Chin Huat ;
>akuster...@gmail.com; sjolley.yp...@gmail.com; Yeoh, Ee Peng
>; Tummalapalli, Vineela
>
>Subject: Re: QA notification for completed autobuilder build (yocto-2.6.3.rc1)
>
>On Thu, 2019-08-08 at 03:00 +, 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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] 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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Jain, Sangeeta]

QA cycle report for 2.7.1 RC1:


  1.  No high milestone defects.
  2.  Test results are available at following location:

  • For results of all automated tests, please 
refer to results at public AB [1]

  • For other test results, refer to git repo " 
yocto-testresults-contrib" [2]

  • For test report for test cases run by Intel and 
WR team, refer to git repo " yocto-testresults-contrib" [2]

  1.  No new defects are found in this cycle. Hardware specific issues are 
observed (Parselog and Xorg failures), but no bugs are filed as these are not 
real Yocto failures.
  2.  ptest failing in this release which were passing in previous release – 
gstreamer[3]. Timeout issues observed in ptest - mdadm [4].
  3.  Summary of ptest in this build:

   qemux86-64-ptest

  Total : 44600

  Pass : 42294

   Fail :  290

 Skip : 2016

  Timeout issues in mdadm

=== Links 



[1] - https://autobuilder.yocto.io/pub/releases/yocto-2.7.1.rc1/testresults/



[2] - 
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults



[3] - [QA 2.7.1.rc1] gstreamer1.0.pipelines/seek ptest failure

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13429



[4] - mdadm ptest times out

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13368




Thanks & Regards,
Sangeeta Jain

 Forwarded Message 
Subject:

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

Date:

Mon, 1 Jul 2019 03:08:44 +

From:

Poky Build User 


To:

yocto@yoctoproject.org

CC:

ota...@ossystems.com.br, 
yi.z...@windriver.com, 
apoorv.san...@intel.com, 
ee.peng.y...@intel.com, 
aaron.chun.yew.c...@intel.com, 
chin.huat@intel.com, 
richard.pur...@linuxfoundation.org, 
akuster...@gmail.com, 
sjolley.yp...@gmail.com, 
sangeeta.j...@intel.com




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


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


Build hash information:
bitbake: 34ed28a412af642a993642c14bd8b95d5ef22cd8
meta-gplv2: 460ba027fd79b99151f95c826446f3aead5d17ff
meta-intel: e84c763090f91196a5d234f62ee39bcf296c7f2e
meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4
oecore: 886deb4d0919c7a81036ea14fb8fd0f1619dd3a3
poky: 38d5c8ea98cfa49825c473eba8984c12edf062be



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: 
richard.pur...@linuxfoundation.org
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Jain, Sangeeta]

Hello All,



Intel and WR YP QA is planning for QA execution for YP build 2.7.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. Coffee Lake

3. NUC 7

4. NUC 6

5. Edgerouter

6. MPC8315e-rdb

7. Beaglebone



ETA for completion is Friday, 5 July.


Thanks & Regards,
Sangeeta Jain


 Forwarded Message 
Subject:

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

Date:

Mon, 1 Jul 2019 03:08:44 +

From:

Poky Build User 


To:

yocto@yoctoproject.org

CC:

ota...@ossystems.com.br, 
yi.z...@windriver.com, 
apoorv.san...@intel.com, 
ee.peng.y...@intel.com, 
aaron.chun.yew.c...@intel.com, 
chin.huat@intel.com, 
richard.pur...@linuxfoundation.org, 
akuster...@gmail.com, 
sjolley.yp...@gmail.com, 
sangeeta.j...@intel.com




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


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


Build hash information:
bitbake: 34ed28a412af642a993642c14bd8b95d5ef22cd8
meta-gplv2: 460ba027fd79b99151f95c826446f3aead5d17ff
meta-intel: e84c763090f91196a5d234f62ee39bcf296c7f2e
meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4
oecore: 886deb4d0919c7a81036ea14fb8fd0f1619dd3a3
poky: 38d5c8ea98cfa49825c473eba8984c12edf062be



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


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Jain, Sangeeta]

QA cycle report for 2.8 M1 RC2:

1. No high milestone defects.  
2. Test results are available at following location:
• For results of all automated tests, please refer to results 
at public AB [1]
• For other test results, refer to git repo " 
yocto-testresults-contrib" [2]
• For test report for test cases run by Intel and WR team, 
refer to git repo " yocto-testresults-contrib" [2]
3. 3 new defects are found in this cycle, BSP HW - parselog issue 
[3], BSP HW - audio issue [4], qemux86 oe-selftest failure on AB [5] 
4. ptests failing in this release which were passing in previous 
release - acl [6]. 3 timeout issues observed in ptests - acl [7], bluez5 [8]  
and mdadm [9].
Richard's comments on ptest failures:  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.
Summary of ptest in this build: 
qemuarm64-ptest:
Total : 435597
Pass : 433344
 Fail :  65
Skip : 2188
Timeout issues in bluez5 and mdadm
qemux86-64-ptest
Total : 45346
Pass : 43235
 Fail :  56
Skip : 2055
Timeout issues in acl, bluez5 and mdadm

5. Summary of ltp test run in this build:
qemuarm64-ltp
Total : 1886
Pass : 1759
 Fail :  127
  qemux86-64-ltp
Total : 1879
 Pass : 1825
 Fail :  54

=== Links 

[1] - https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2/testresults/

[2] - git clone g...@push.yoctoproject.org:yocto-testresults-contrib -b zeus

[3] - [QA 2.8 M1 RC1][BSP HW] parselogs.ParseLogsTest.test_parselogs failure on 
coffeelake
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13396

[4] - [QA 2.8 M1 RC1][BSP HW] audio is not playing on coffeelake and nuc7
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13397

[5] - [QA 2.8 M1 RC1] test_boot_machine_slirp is showing error for qemux86
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13399

[6] - [QA 2.8 M1 RC1] acl ptest failure
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13395

[7] - acl ptest timeout due to perl update
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13391

[8] - bluez5 ptest hangs with gcc 9
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13366

[9] - mdadm ptest times out
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13368


Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [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.pur...@linuxfoundation.org 
>Sent: Tuesday, 11 June, 2019 4:51 PM
>To: pokybu...@debian9-ty-1.yocto.io; yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; akuster...@gmail.com; sjolley.yp...@gmail.com;
>Jain, Sangeeta 
>Subject: Re: QA notification for completed autobuilder build (yocto-2.8_M1.rc2)
>
>On Tue, 2019-06-11 at 03:32 +, pokybu...@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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Jain, Sangeeta]

>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Wednesday, 12 June, 2019 4:05 PM
>To: Jain, Sangeeta ; pokybuild@debian9-ty-
>1.yocto.io; yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; akuster...@gmail.com; sjolley.yp...@gmail.com
>Subject: Re: QA notification for completed autobuilder build (yocto-2.8_M1.rc2)
>
>On Wed, 2019-06-12 at 00:51 +, Jain, Sangeeta wrote:
>> On Tue, 2019-06-11 at 03:32 +, pokybu...@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:
>> Thanks Richard for sharing this.
>> > 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.
>>
>> We are analysing the failures and will file the bugs as suggested.
>
>Just for reference I did file some of the bugs.
>
>> > 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.
>>
>> Looks like some disconnect here. In test result report, no timeout
>> issue reported for acl ptest.
>
>https://autobuilder.yocto.io/pub/releases/yocto-
>2.8_M1.rc2/testresults/testresult-report.txt
>
>acl  | 184 | 9| 0 | 302 T
>
>I hadn't spotted that dbus-test also has a timeout :(.
>
>This timeout is also in the testresults file:
>
>ERROR: Exit status is 9\nDURATION: 302\nTIMEOUT: /usr/lib/acl/ptest\n
>
>in:
>
>https://autobuilder.yocto.io/pub/releases/yocto-
>2.8_M1.rc2/testresults/qemux86-64-ptest/testresults.json
>
>> We are referring to test results at yocto-testresults under tag "
>> master/54573-g9910a3631ce953b8dd8f3d57d6e122c7fd8cb462/1"
>
>You are right, there is no mention of this in the log at:
>
>http://git.yoctoproject.org/cgit.cgi/yocto-
>testresults/tree/runtime/poky/qemux86-64/core-image-sato-sdk-ptest/ptest-
>acl.log?id=56b1caa6044ce30e92a1895eae48d3935562b627
>or
>http://git.yoctoproject.org/cgit.cgi/yocto-
>testresults/commit/runtime/poky/qemux86-64/core-image-sato-sdk-ptest/ptest-
>acl.log?id=ac623e13e3bc3a348b60fe3b884e6ae567b8230a
>
>I suspect this is due to the information being filtered out as part of the log
>processing. We probably shouldn't do that.
>
>Looking at the individual logs in 
>https://autobuilder.yocto.io/pub/releases/yocto-
>2.8_M1.rc2/testresults/qemux86-64-ptest/testresults.json, the timeout
>information looks to be truncated off there too.
>
>I do however note that:
>
>"ptestresult.sections": {
>"acl": {
>"duration": "302",
>"exitcode": "9",
>"timeout": true
>},
>
>is in http://git.yoctoproject.org/cgit.cgi/yocto-
>testresults/tree/runtime/poky/qemux86-64/core-image-sato-sdk-
>ptest/testresults.json?id=56b1caa6044ce30e92a1895eae48d3935562b627
>so the timeout is recorded in the results.

Thanks. Able to trace all time-out issues, including dbus-test !
>
>Regards,
>
>Richard
>

Thanks & Regards,
Sangeeta Jain
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[Jain, Sangeeta]

>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Tuesday, 11 June, 2019 4:51 PM
>To: pokybu...@debian9-ty-1.yocto.io; yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; akuster...@gmail.com; sjolley.yp...@gmail.com;
>Jain, Sangeeta 
>Subject: Re: QA notification for completed autobuilder build (yocto-2.8_M1.rc2)
>
>On Tue, 2019-06-11 at 03:32 +, pokybu...@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:
Thanks Richard for sharing this.
>
>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.

We are analysing the failures and will file the bugs as suggested.
>
>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.

Looks like some disconnect here. In test result report, no timeout issue 
reported for acl ptest.
We are referring to test results at yocto-testresults under tag " 
master/54573-g9910a3631ce953b8dd8f3d57d6e122c7fd8cb462/1"
>
>There is a lot more testing happening under automation than in previous builds,
>particularly on arm hosts/targets.
Thanks for increased coverage.

>
>Cheers,
>
>Richard

Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] QA cycle report for 2.7 RC2

[Jain, Sangeeta]

Hi Armin,

From: akuster808 
Sent: Friday, 26 April, 2019 10:30 PM
To: Jain, Sangeeta ; 'yocto@yoctoproject.org' 
; Eggleton, Paul ; 
'richard.pur...@linuxfoundation.org' ; 
'Michael Halstead' ; Erway, Tracey M 
; 'sjolley.yp...@gmail.com' 
; openembedded-c...@lists.openembedded.org
Subject: Re: [OE-core] QA cycle report for 2.7 RC2

Sangeeta,

On 4/25/19 11:27 PM, Jain, Sangeeta wrote:

QA cycle report for 2.7 RC2:


  1.  No high milestone defects.
  2.  Test results are available at following location:
*For results of all automated tests, please refer to results at public 
AB [1].
*For other test results, refer to attachment [2].
*For test report for test cases run by Intel and WR team, refer 
attachment [3]
Since "compliance-test.compliance-test.LSB_subset_test_suite" was run, can you 
share the changes made to /opt/lsb-test/session file?

For "compliance-test.compliance-test.LSB_subset_test_suite", we follow the 
procedure as mentioned at https://wiki.yoctoproject.org/wiki/BSP_Test_Plan
Under compliance section.  Changes to /opt/lsb-test/session file are also 
handled by script "compliance_test.py" (link to which you can find in wiki page 
mentioned)


Can I get clarification on how 
"compliance-test.compliance-test.stress_test_-_ltp_-Beaglebone" was run?

To run stress test, we use "./runltp -f crashme" command.
Stress test for Beaglebone is run by Windriver team. Adding Yi Zhao in mail.



Regards,
Armin

*For full test report, refer attachment [4]

  1.  No new defects are found in this cycle.
  2.  No existing issues observed in this release
  3.  No ptests are failing in this release which were passing in previous 
release. No timeout issues.

QA Hint: One failure was observed on public AB:

testseries | result_id : qemuppc | oeselftest_centos-7_qemuppc_20190414221329
runqemu.QemuTest.test_qemu_can_shutdown


No bug filed for this issue, as it appears to be an intermittent failure and 
worked on rc1 test run.

=== Links 

Link to testresults:

[1] - https://autobuilder.yocto.io/pub/releases/yocto-2.7.rc2/testresults/

[2] - 2.7_RC2_results_merged.zip

[3] - 2.7_ rc2_intel_wr_merged_report

[4] - 2.7 _rc2_full_report

Thanks & Regards,
Sangeeta Jain




-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA cycle report for 2.5.3 RC3

[Jain, Sangeeta]

>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Tuesday, 23 April, 2019 10:31 PM
>To: Jain, Sangeeta ; 'yocto@yoctoproject.org'
>; Eggleton, Paul ; 'Michael
>Halstead' ; Erway, Tracey M
>; 'sjolley.yp...@gmail.com'
>; 'openembedded-core-
>requ...@lists.openembedded.org' requ...@lists.openembedded.org>
>Cc: Sangal, Apoorv ; Yeoh, Ee Peng
>; Graydon, Tracy ;
>Tummalapalli, Vineela 
>Subject: Re: QA cycle report for 2.5.3 RC3
>
>On Thu, 2019-04-18 at 04:58 +, Jain, Sangeeta wrote:
>>
>> QA cycle report for 2.5.3 RC3:
>>
>> No high milestone defects.
>> Test results are available at following location:
>> ·For results of all automated tests, refer to results at
>> public AB [1].
>> ·For other test results, refer to attachment [2].
>> ·For test report for test cases run by Intel and WR team,
>> refer attachment [3]
>> ·For full test report, refer attachment [4]
>> ·For ptest results, please refer to results at public AB [5]
>> ·For ptest report, refer to attachment [6]
>> No new defects are found in this cycle.
>> Number of existing issues observed in this release is 2- toaster [7]
>> and Build-appliance [8] For ptest, regression data is not available
>> for this release. No timeout issues.
>> Test result report on Public AB shows no failures.
>
>I've been discussing with Tracy and Vineela how to best handle the test 
>results for
>the release for 2.5.3. In the end I:
>
>a) Copied in the ptest results to the right place. This will happen 
>automagically in
>all future builds:
>
>https://autobuilder.yocto.io/pub/releases/yocto-2.5.3/testresults/qemux86-64-
>ptest/

>
>b) Copied in the intel test results to their own directory:
>
>https://autobuilder.yocto.io/pub/releases/yocto-2.5.3/testresults-intel/
>
>c) Manually generated an updated test report for the combined results with the
>commands:
>
>$ cd /srv/autobuilder/autobuilder.yoctoproject.org/pub/releases/yocto-2.5.3
>$resulttool report . > testreport.txt
>
>d) Added a header to the report which consisted of the report from QA with
>details of the bugs etc.
>
>This means we have a top level testreport file which contains all the test
>information about the release.
>
>I'd like to make this the standard procedure for release. The release notes and
>announcement can refer to the test report included with the release and the 
>test
>results as its there all together.
>
>Ultimately I'd like to improve the formatting of the report (separate out ptest
>regressions from the other regressions, maybe html, maybe graphs, better
>regression information) but that is something for the future.
>
>Does that work for everyone?

That looks great to me. 
As a further improvement for sharing of test results, I am working to create a 
wiki page for consolidated 
test results. For 2.5.3, it can be viewed at:
https://wiki.yoctoproject.org/wiki/WW16_-_2019-04-18_-_Full_Test_Cycle_2.5.3_RC3

After you have added more results on AB, I will change some existing links on 
this web page with the new ones.

Another thought I have is that since for any release, all data will be removed 
from public AB after few days of release,
Should I include here a  link to "yocto-testresults" git repo? It will make 
this wiki page more useful for reference in future as well.



>
>Cheers,
>
>Richard
>
Thanks & Regards,
Sangeeta Jain
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 2.6.2 (thud 20.0.2) Released

[Jain, Sangeeta]

For latest releases and test results please refer to:

https://autobuilder.yocto.io/pub/releases/

For previous test results, refer to yocto-testresults repo at 

https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults/

to refer 2.6.2.rc3 results from yocto-testresults, use

--branch thud  --commit faeb366bc3eb322f5f203cfe08dc4cf529a822e9


Thanks & Regards,
Sangeeta Jain

>-Original Message-
>From: yocto-boun...@yoctoproject.org  On
>Behalf Of Manjukumar Harthikote Matha
>Sent: Thursday, 18 April, 2019 4:28 AM
>To: Graydon, Tracy ; yocto-
>annou...@yoctoproject.org; yocto@yoctoproject.org
>Subject: Re: [yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 2.6.2
>(thud 20.0.2) Released
>
>Hi Tracy,
>
>> -Original Message-
>> From: yocto-announce-boun...@yoctoproject.org [mailto:yocto-announce-
>> boun...@yoctoproject.org] On Behalf Of Tracy Graydon
>> Sent: Wednesday, April 17, 2019 1:25 PM
>> To: yocto-annou...@yoctoproject.org; yocto@yoctoproject.org
>> Subject: [yocto-announce] [ANNOUNCEMENT] Yocto Project 2.6.2 (thud
>> 20.0.2) Released
>>
>> We are pleased to announce the latest release of the Yocto Project
>> 2.6.2 (thud-
>> 20.0.2) is now available for download:
>>
>> http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.2/poky-thud
>> -
>> 20.0.2.tar.bz2
>> http://mirrors.kernel.org/yocto/yocto/yocto-2.6.2/poky-thud-20.0.2.tar
>> .bz2
>>
>> A gpg signed version of these release notes is available at:
>>
>> http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.2/RELEASENO
>> TES
>>
>> Yocto 2.6.2 QA reporting:
>>
>> Summary: https://lists.yoctoproject.org/pipermail/yocto/2019-
>> April/044827.html
>> Results:
>> https://autobuilder.yocto.io/pub/releases/yocto-2.6.2.rc3/testresults/
>>
>
>I am not able to access this results page. It says "No Such Resource File not
>found."
>
>
>Thanks,
>Manju
>
>
>> Build log:
>> hhttps://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/122
>>
>> Release Criteria:
>> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.6_Status#Yocto_Pro
>> ject_2
>> .6.2_release
>>
>>
>> Thank you for everyone's contributions to this release.
>>
>> Sincerely,
>>
>> Tracy Graydon
>> Yocto Project Build and Release
>> tracy.gray...@intel.com
>> --
>> ___
>> yocto-announce mailing list
>> yocto-annou...@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto-announce
>--
>___
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.7.rc2)

[Jain, Sangeeta]

Hello All,

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

OEQA-Manual tests for following modules:
1.SDK
2.Kernel
3.   Toaster
4.   Bitbake (oe-core)
5.   Build-appliance
6.   Crops
7.   Compliance-test
8.   Bsp-hw
9.   Bsp-qemu

Runtime auto test for following platforms:

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

ETA for completion is Friday, 26 April.

Thanks & Regards,
Sangeeta Jain

>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Monday, 15 April, 2019 4:45 PM
>To: yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
>; Yeoh, Ee Peng ; Chan,
>Aaron Chun Yew ; Ang, Chin Huat
>; akuster...@gmail.com; sjolley.yp...@gmail.com;
>Jain, Sangeeta 
>Subject: Re: QA notification for completed autobuilder build (yocto-2.7.rc2)
>
>On Sun, 2019-04-14 at 23:48 +, pokybuild@centos7-ty-1.localdomain
>wrote:
>> A build flagged for QA (yocto-2.7.rc2) was completed on the
>> autobuilder and is available at:
>>
>>
>> https://autobuilder.yocto.io/pub/releases/yocto-2.7.rc2
>>
>>
>> Build hash information:
>>
>> bitbake: cb185efe9e88cfb12b7a3fd08f3086ca0b69c8e2
>> meta-gplv2: 106ba6d2a4d08a276205c305f8485d701fe8a8f3
>> meta-intel: cd2c3bfca97655999cbde645b73be712675dba92
>> meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4
>> oecore: f571b188177788d8ed0a7f3efe3569f153b1b0d3
>> poky: 0e392026ffefee098a890c39bc3ca1f697bacb52
>
>Note for QA:
>
>I was able to add the automated oe-selftests for the different qemu machines in
>this run as we discussed. This should reduce the amount of tests QA need to 
>run.
>There was one failure:
>
>testseries | result_id : qemuppc | oeselftest_centos-
>7_qemuppc_20190414221329
>runqemu.QemuTest.test_qemu_can_shutdown
>
>I believe this worked on the rc1 test run so it appears to be an intermittent 
>failure
>which I'd not block release on.
>
>Cheers,
>
>Richard

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA cycle report for 2.6.2 RC3

[Jain, Sangeeta]

>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Friday, 12 April, 2019 6:58 PM
>To: Jain, Sangeeta ; 'yocto@yoctoproject.org'
>; Eggleton, Paul ; 'Michael
>Halstead' ; Erway, Tracey M
>; 'sjolley.yp...@gmail.com'
>; openembedded-core-
>requ...@lists.openembedded.org
>Cc: Sangal, Apoorv ; Yeoh, Ee Peng
>
>Subject: Re: QA cycle report for 2.6.2 RC3
>
>On Wed, 2019-04-10 at 02:38 +, Jain, Sangeeta wrote:
>>
>> QA cycle report for 2.6.2 RC3:
>>
>> No high milestone defects.
>> Test results are available at following location:
>> ·For results of all automated tests, refer to results at
>> public AB [1].
>> ·For other test results, refer to attachment [2].
>> ·For test report for test cases run by Intel and WR team,
>> refer attachment [3]
>> ·For full test report, refer attachment [4]
>> ·For ptest results, please refer to results at public AB [5]
>> ·For ptest report, refer to attachment [6]
>> 1 new defects are found in this cycle, Beaglebone [7].
>> QA hint:  Similar issue for sysemtap failure (bug 13153) was found in
>> 2.7 M2 RC1 which is now resolved for master.
>> Number of existing issues observed in this release is 3- toaster [8],
>> Build-appliance [9] and qemu-shutdown [10] For ptest, regression data
>> is not available for this release. 3 packages are facing timeout
>> issues: lttng-tools [11], openssh [12] and strace [13].
>> Test result report on Public AB shows following failures:
>> buildgalculator.GalculatorTest.test_galculator
>> QA Comment: Expected failure for hw limitation
>> python.PythonTest.test_python3
>> QA Comment: Failure due to “python3” test case not backported to Thud.
>> No bug filed as not real Yocto failure.
>
>Thanks for running QA on this. Firstly, I can comment on the bugs:
>
>> [7] Bug 13273 - [2.6.2 RC3] Systemtap doesn't work on beaglebone
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13273
>
>We've root caused this on master and believe we know how to fix this, its a
>kernel makefile configuration issue. We can likely document this as a known 
>issue
>and fix in 2.6.3.
>
>> Previous Bugs observed in this release:
>>
>> [8] Bug 13191 – [Test Case 1439] Build Failure after adding or
>> removing packages with and without dependencies
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13191
>>
>> [9] Bug 12991 - [Bug] [2.6 M4 RC1][Build-Appliance] Bitbake build-
>> appliance-image getting failed during building image due to webkitgtk
>> package.
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991
>
>This is a long running issue we've been "ignoring", its likely resource issues 
>on the
>machine/VM running the test.
>
>> [10] Bug 13234 - [2.7 M3 RC1] qemumips & qemumips64: failed to
>> shutdown
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13234
>
>This is an issue root caused to be from 4.19 and 5.0 kernels. I thought
>2.6.2 had a 4.18 kernel so shouldn't have this issue? The bug wasn't reopened?

2.6.2 had shutdown issue with qemuarm. Which is a known issue for 2.6 release 
and marked as won't fix.
Correct bug id for Qemu arm shutdown issue is:

Bug 12499 - [2.5 M1 RC3] qemuarm: failed to shutdown
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12499

Thanks for pointing out!

>
>> ptest Bugs:
>>
>> [11] Bug 13255 - [2.7 M3 rc1] lttng-tools ptest facing timeout issue
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13255
>>
>> [12] Bug 13256 - [2.7 M3 rc1] openssh ptest facing timeout issue
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13256
>>
>> [13] Bug 13274 - [2.6.2 RC3] strace ptest facing timeout issue
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13274
>
>ptest has been a bit tricky and we've been actively working these bugs on 
>master.
>Once we have them resolved there we can backport to older releases.
>
>There is one other critical issue we have with 2.6.2 which is the revert of the
>boost upgrade. I'm very reluctant to release without that revert as it caused
>problems for a lot of people.
>
>I'm wondering whether we should rebuild 2.6.2 one commit later and then
>release that assuming it passes a rerun of the automated QA (but not the manual
>QA). Opinions on that?
>
>I'd propose fixing the systemtap and ptest issues for 2.6.3.
>
>Cheers,
>
>Richard
>
>


Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.5.3.rc3)

[Jain, Sangeeta]

Hello All,

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

OEQA-Manual tests for following modules:
1.  SDK
2.  Eclipse-plugin
3.  Kernel
4.  Toaster
5.  Bitbake (oe-core)
6.  Build-appliance
7.  Crops
8.  Compliance-test
9.  Bsp-hw
10. Bsp-qemu

Runtime auto test for following platforms:

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

Other auto tests:

1.  Qemu-selftest
2.  Qemu-meta-ide

ETA for completion is Thursday, 18 April.

Thanks & Regards,
Sangeeta Jain

>-Original Message-
>From: yocto-boun...@yoctoproject.org  On
>Behalf Of Poky Build User
>Sent: Thursday, 28 March, 2019 1:47 PM
>To: yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; Chan, Aaron Chun Yew
>; akuster...@gmail.com
>Subject: [yocto] QA notification for completed autobuilder build 
>(yocto-2.5.3.rc3)
>
>
>A build flagged for QA (yocto-2.5.3.rc3) was completed on the autobuilder and 
>is
>available at:
>
>
>https://autobuilder.yocto.io/pub/releases/yocto-2.5.3.rc3
>
>
>Build hash information:
>
>bitbake: c0af6c81f8d5487ea2cef54a78fd1cb1d0dc6520
>eclipse-poky-neon: cd86f167be58a11b289af4ef236b4adec57ec316
>eclipse-poky-oxygen: 210c58c5a7147127f9c840718c6cd2a56e871718
>meta-gplv2: d7687d404bbc9ba3f44ec43ea8828d9071033513
>meta-intel: ba5f7ecd26630b74b6338c1828847a64ab172453
>meta-mingw: 628dcfed62ce8dcc408e5b4a5e5c0aaa921b20ad
>meta-qt3: 02f273cba6c25f5cf20cb66d8a417a83772c3179
>meta-qt4: 8e791c40140460825956430ba86b6266fdec0a93
>oecore: 0a2db923fd17019d07d88204b355aa46590f0b97
>poky: 84b78df15ff77b2fe2aeb62fcaa265dce7ebfbbb
>
>
>
>This is an automated message from the Yocto Project Autobuilder
>Git: git://git.yoctoproject.org/yocto-autobuilder2
>Email: richard.pur...@linuxfoundation.org
>
>
>
>--
>___
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

[Jain, Sangeeta]

Hi Richard,


>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Wednesday, 3 April, 2019 5:20 PM
>To: Jain, Sangeeta ; Poky Build User
>; yocto@yoctoproject.org;
>sjolley.yp...@gmail.com; Yi Zhao 
>Cc: ota...@ossystems.com.br; Chan, Aaron Chun Yew
>; akuster...@gmail.com; Yeoh, Ee Peng
>; Sangal, Apoorv 
>Subject: Re: [yocto] QA notification for completed autobuilder build (yocto-
>2.6.2.rc3)
>
>Hi,
>
>This is good information and helps a lot, thanks! I had a question below.
>
>On Wed, 2019-04-03 at 08:06 +, Jain, Sangeeta wrote:
>> Intel and WR YP QA is now working on QA execution for YP build 2.6.2
>> RC3. We are planning to execute following tests for this cycle:
>>
>> OEQA-Manual tests for following modules:
>> 1.   SDK
>> 2.   Eclipse-plugin
>> 3.   Kernel
>> 4.   Toaster
>> 5.   Bitbake (oe-core)
>> 6.   Build-appliance
>> 7.   Crops
>> 8.   Compliance-test
>> 9.   Bsp-hw
>> 10.  Bsp-qemu
>>
>> Runtime auto test for following platforms:
>>
>> 1.   MinnowTurbo 32bit
>> 2.   MinnowTurbot 64 bit
>> 3.   NUC 7
>> 4.   NUC 6
>> 5.   Edgerouter
>> 6.   MPC8315e-rdb
>> 7.   Beaglebone
>> 8.   Qemuarm
>> 9.   Qemuarm-64
>> 10.  Qemuppc
>> 11.  Qemumips
>> 12.  Qemumips64
>
>I'm wondering if there is any difference between items 8-12 here and the 
>runtime
>testing we run on the public autobuilder? Is there some testing we're missing 
>on
>the public autobuilder?

We will be running oe-selftest for machines 8-12, which is missing in 
autobuilder results.

Also, I don't see any ptest results for 2.6.2.rc3 on public autobuilder. Do you 
have any plans to run them and share the results on autobuilder?


>
>Cheers,
>
>Richard
>

Thanks & Regards,
Sangeeta Jain
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.2.rc3)

[Jain, Sangeeta]

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

OEQA-Manual tests for following modules:
1.  SDK
2.  Eclipse-plugin
3.  Kernel
4.  Toaster
5.  Bitbake (oe-core)
6.  Build-appliance
7.  Crops
8.  Compliance-test
9.  Bsp-hw
10. Bsp-qemu

Runtime auto test for following platforms:

1.  MinnowTurbo 32bit
2.  MinnowTurbot 64 bit
3.  NUC 7
4.  NUC 6
5.  Edgerouter
6.  MPC8315e-rdb
7.  Beaglebone
8.  Qemuarm
9.  Qemuarm-64
10. Qemuppc
11. Qemumips
12. Qemumips64

Other auto tests: 

1.  Qemu-selftest
2.  Qemu-meta-ide

ETA for completion is Wednesday, 10 April.

Thanks & Regards,
Sangeeta Jain

>-Original Message-
>From: yocto-boun...@yoctoproject.org  On
>Behalf Of Poky Build User
>Sent: Thursday, 28 March, 2019 11:30 AM
>To: yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; Chan, Aaron Chun Yew
>; akuster...@gmail.com
>Subject: [yocto] QA notification for completed autobuilder build 
>(yocto-2.6.2.rc3)
>
>
>A build flagged for QA (yocto-2.6.2.rc3) was completed on the autobuilder and 
>is
>available at:
>
>
>https://autobuilder.yocto.io/pub/releases/yocto-2.6.2.rc3
>
>
>Build hash information:
>
>bitbake: 7c1eb51d1e8a4c5f39bf9dddf05fb0b3598da72b
>eclipse-poky-neon: cd86f167be58a11b289af4ef236b4adec57ec316
>eclipse-poky-oxygen: 210c58c5a7147127f9c840718c6cd2a56e871718
>meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575
>meta-intel: 27dadcfc7bc0de70328b02fecb841608389d22fc
>meta-mingw: 6556cde16fbdf42c7edae89bb186e5ae4982eff5
>meta-qt3: 23d7543ebd7e82ba95cbe19043ae4229bdb3b6b1
>meta-qt4: b37d8b93924b314df3591b4a61e194ff3feb5517
>oecore: 45032e30be70503faeee468159b216031b729309
>poky: faeb366bc3eb322f5f203cfe08dc4cf529a822e9
>
>
>
>This is an automated message from the Yocto Project Autobuilder
>Git: git://git.yoctoproject.org/yocto-autobuilder2
>Email: richard.pur...@linuxfoundation.org
>
>
>
>--
>___
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA cycle report for 2.7 M3 RC1

[Jain, Sangeeta]

Hi Richard,

For oe-selftest -r runqemu,meta_ide, configuration we are using is only 
changing the machine type.

For adding "who" identifier in resulttool command, we can take it up as an 
enhancement.

Thanks & Regards,
Sangeeta Jain

>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Wednesday, 3 April, 2019 2:32 AM
>To: Jain, Sangeeta ; 'yocto@yoctoproject.org'
>; Eggleton, Paul ; 'Michael
>Halstead' ; Erway, Tracey M
>; sjolley.yp...@gmail.com; Burton, Ross
>
>Cc: OTC Embedded Malaysia 
>Subject: Re: QA cycle report for 2.7 M3 RC1
>
>Hi Sangeeta/Ee Peng,
>
>On Tue, 2019-04-02 at 05:02 +, Jain, Sangeeta wrote:
>> QA cycle report for 2.7 M3 RC1:
>>
>> No high milestone defects.
>> This is completion of first QA cycle after adoption of new QA process.
>> Test results are available at following location:
>> ·For results of all automated tests, please refer to results
>> at public AB [1].
>> ·For other test results, refer to attachment [2].
>> ·For test report for test cases run by Intel and WR team,
>> refer attachment [3]
>> ·For full test report, refer attachment [4]
>> 2 new defects are found in this cycle, oe-selftest [5] and qemu-
>> shutdown[6].
>> Number of existing issues observed in this release is 3- toaster [7],
>> Build-appliance [8] and Beaglebone [9] For ptest, 3 package tests are
>> failing in this release which were passing in previous release: python
>> [10], python3[11] and strace[12].
>> 3 packages are facing timeout issues: lttng-tools [13], openssh [14]
>> and python3 [15].
>
>Thanks for this. I have some questions/observations.
>
>Looking at the Intel/WR report, I see tests which start oeselftest_XXX for sdk-
>extras and qemu-shutdown. I think this means you have some QA test
>infrastructure running "oe-selftest -r runqemu,meta_ide", iterating over
>MACHINE=qemuppc, qemumips, qemuarm, qemux86?
>
>Is this some automation we're missing in the autobuilder configuration?
>We all other tests covered and this is the only remaining automated piece we
>haven't covered? What configuration are we missing exactly for the missing
>tests?

Just run for MACHINE=qemuppc /qemumips / qemuarm / qemux86

>
>I'm partly wondering how you found the shutdown issue but this would explain
>that.
>
>I think going forward we need to add some kind of "who" identifier to the test
>results so we can say where/who they came from (main autobuilder, Intel, WR,
>anywhere else). We could add a resulttool command to "stamp" a set of test
>results with this, maybe as a parameter to the store command?

Will work on resulttool to add this enhancement. Though not sure about timeline 
as of now.

>
>Of the bugs, I didn't see any which I think should block M3, I think we 
>probably
>should release that and move forward to M4. I do want to see some of these
>fixed before we build M4 though. I've made comments on them below.
>
>> New Bugs :
>>
>> [5] Bug 13237 - [2.7 M3 RC1][OE-selftest][Opensuseleap 15.0][Public
>> AB]:"test_wic_cp_ext" failing for Opensuseleap 15.0.
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13237
>
>Ross: Are you looking into that one?
>
>> [6] Bug 13234 - [2.7 M3 RC1] qemumips & qemumips64: failed to shutdown
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13234
>
>This needs looking into and fixing, as well as figuring out why the autobuilder
>doesn't see this (see above for my hypothesis).
>
>> Previous Bugs observed in this release:
>>
>> [7] Bug 13191 – [Test Case 1439] Build Failure after adding or
>> removing packages with and without dependencies
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13191
>>
>> [8] Bug 12991 - [Bug] [2.6 M4 RC1][Build-Appliance] Bitbake build-
>> appliance-image getting failed during building image due to webkitgtk
>> package.
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991
>
>We need to do something about this. I believe its related to resource 
>starvation in
>the VM.
>
>> [9] Bug 13153 – [2.7 M2 RC1] Systemtap doesn't work on beaglebone
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13153
>
>I'm hoping a SRCREV bump for beaglebone-yocto fixes this.
>
>> ptest Bugs:
>>
>> [10] Bug 13249 - [2.7 M3 RC1] python ptest failure
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13249
>
>I'm hoping a patch from Ross in master fixes this, need to retest ptest with 
>this
>applied.
>
>> [11] Bug 13253 - [2.7 M3 RC1] python3 ptest failure
>> https://bugzilla.yoctoproject.org/show

[yocto] QA cycle report for 2.7 M2 RC2

[Jain, Sangeeta]

The final corrected report is as follows:





This is the full report for 2.7 M2 RC2:





=== Summary 



All planned tests were executed.

Total Test Executed - 3624

Passed Test - 3607

Failed Test - 9





There were zero high milestone defect.  Team had found 2 new defects in 
Toaster[1] and BSP[2].

3 existing issues were observed in this release.



For ptest, there is a drop in percentage of pass rate for 3 modules: nettle, 
perl and python3. Bugs are reported for Nettle [3] and Perl [4]. For python3, 
no bug is filed, since there is a decrease in percentage but no failures as 
compared to previous results.



=== QA-Hints



  1.  No high milestone defect.
  2.  CROPS manual test cases (total no 6) is replaced by one consolidated auto 
test case in this test cycle.

=== Bugs 



New Bugs

[1] Bug 13191 - [2.7 M2 RC1] Systemtap doesn't work on beaglebone

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13191


[2] Bug 13178 -  [2.7 M2 RC2] X server and matchbox desktop don't start up 
properly on beaglebone



https://bugzilla.yoctoproject.org/show_bug.cgi?id=13178







ptest Bugs:



[3] Bug 13193 - [2.7 M2 RC2] nettle ptest failure

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13193



[4] Bug 13194 - [2.7 
M2 RC2] perl ptest failure

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13194





Previous Bugs observed in this release:

[5] Bug 13153 - [2.7 M2 RC1] Systemtap doesn't work on beaglebone

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13153





[6] Bug 12991 - [Bug] 
[2.6 M4 RC1][Build-Appliance] Bitbake build-appliance-image getting failed 
during building image due to webkitgtk package.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991



[7] Bug 12499 - [Bug] 
[2.5 M1 RC3] qemuarm: failed to shutdown.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12499






Thanks & Regards,
Sangeeta Jain
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA cycle report for 2.7 M2 RC2

[Jain, Sangeeta]

corrected bug summary:


[2] Bug 13178 - [2.7_m2_rc2][compliance test][LSB Test] "Failed to load module 
Core_test.pm, samba_test.pm", LSB Test has failed"

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13178


Thanks & Regards,
Sangeeta Jain

From: Jain, Sangeeta
Sent: Monday, 25 February, 2019 9:49 AM
To: 'yocto@yoctoproject.org' ; Eggleton, Paul 
; 'richard.pur...@linuxfoundation.org' 
; 'Michael Halstead' 
; Erway, Tracey M ; 
sjolley.yp...@gmail.com
Cc: OTC Embedded Malaysia ; Greenberg, Suzy M 

Subject: QA cycle report for 2.7 M2 RC2


Hello All,



This is the full report for 2.7 M2 RC2:





=== Summary 



All planned tests were executed.

Total Test Executed - 3624

Passed Test - 3607

Failed Test - 9





There were zero high milestone defect.  Team had found 2 new defects in 
Toaster[1] and BSP[2].

3 existing issues were observed in this release.



For ptest, there is a drop in percentage of pass rate for 3 modules: nettle, 
perl and python3. Bugs are reported for Nettle [3] and Perl [4]. For python3, 
no bug is filed, since there is a decrease in percentage but no failures as 
compared to previous results.



=== QA-Hints



  1.  No high milestone defect.
  2.  CROPS manual test cases (total no 6) is replaced by one consolidated auto 
test case in this test cycle.

=== Bugs 



New Bugs

[1] Bug 13191 - [2.7 M2 RC1] Systemtap doesn't work on beaglebone

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13191



[2] Bug 13178 - [2.7_m2_rc1][compliance test][LSB Test] "Failed to load module 
Core_test.pm, samba_test.pm", LSB Test has failed"

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13178







ptest Bugs:



[3] Bug 13193 - [2.7 M2 RC2] nettle ptest failure

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13193



[4] Bug 13194<https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991> - [2.7 
M2 RC2] perl ptest failure

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13194





Previous Bugs observed in this release:

[5] Bug 13153 - [2.7 M2 RC1] Systemtap doesn't work on beaglebone

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13153





[6] Bug 12991<https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991> - [Bug] 
[2.6 M4 RC1][Build-Appliance] Bitbake build-appliance-image getting failed 
during building image due to webkitgtk package.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991



[7] Bug 12499<https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991> - [Bug] 
[2.5 M1 RC3] qemuarm: failed to shutdown.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12499






Thanks & Regards,
Sangeeta Jain
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA cycle report for 2.7 M2 RC2

[Jain, Sangeeta]

Hello All,



This is the full report for 2.7 M2 RC2:





=== Summary 



All planned tests were executed.

Total Test Executed - 3624

Passed Test - 3607

Failed Test - 9





There were zero high milestone defect.  Team had found 2 new defects in 
Toaster[1] and BSP[2].

3 existing issues were observed in this release.



For ptest, there is a drop in percentage of pass rate for 3 modules: nettle, 
perl and python3. Bugs are reported for Nettle [3] and Perl [4]. For python3, 
no bug is filed, since there is a decrease in percentage but no failures as 
compared to previous results.



=== QA-Hints



  1.  No high milestone defect.
  2.  CROPS manual test cases (total no 6) is replaced by one consolidated auto 
test case in this test cycle.

=== Bugs 



New Bugs

[1] Bug 13191 - [2.7 M2 RC1] Systemtap doesn't work on beaglebone

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13191



[2] Bug 13178 - [2.7_m2_rc1][compliance test][LSB Test] "Failed to load module 
Core_test.pm, samba_test.pm", LSB Test has failed"

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13178







ptest Bugs:



[3] Bug 13193 - [2.7 M2 RC2] nettle ptest failure

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13193



[4] Bug 13194 - [2.7 
M2 RC2] perl ptest failure

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13194





Previous Bugs observed in this release:

[5] Bug 13153 - [2.7 M2 RC1] Systemtap doesn't work on beaglebone

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13153





[6] Bug 12991 - [Bug] 
[2.6 M4 RC1][Build-Appliance] Bitbake build-appliance-image getting failed 
during building image due to webkitgtk package.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991



[7] Bug 12499 - [Bug] 
[2.5 M1 RC3] qemuarm: failed to shutdown.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12499






Thanks & Regards,
Sangeeta Jain
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA cycle report for 2.7 M2 RC1

[Jain, Sangeeta]

Hello All,



This is the full report for 2.7 M2 RC1:



https://wiki.yoctoproject.org/wiki/WW01_-_2019-01-28_-_Full_Test_Cycle_2.7_M2_RC1



=== Summary 



All planned tests were executed.

Total Test Executed - 3629

Passed Test - 3613

Failed Test - 16





There were zero high milestone defect.  Team had found 3 new defects in BSP[1], 
Compliance [2] and  OE-Core[3].

5 existing issues were observed in this release.



For ptest, there is a drop in percentage of pass rate for 3 modules: nettle, 
perl and valgrind. Bugs are reported for Nettle [4] and Perl [5]. For Valgrind, 
no bug is filed, since there is a decrease in percentage but no failures as 
compared to previous results.



=== QA-Hints



  1.  No high milestone defect.
  2.  For performance test results, this time there is a new machine "pokybuild 
at perf-centos7.yoctoproject.org" introduced in performance test results from 
Yocto-perf mailing list. And results from "Yocto CentOS 7 Build Perf Tester" is 
missing for this release. Hence, the comparison between results from two 
"centos7" machines shows huge differences.



=== Bugs 



New Bugs

[1] Bug 13153 - [2.7 M2 RC1] Systemtap doesn't work on beaglebone

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13153



[2] Bug 13160 - [2.7_m2_rc1][compliance test][LSB Test] "Failed to load module 
Core_test.pm, samba_test.pm", LSB Test has failed"

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13160



[3] Bug 13161 - [2.7 M2 RC1] Perl can not handle signals

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13161



ptest Bugs:



[4] Bug 13155 - [2.7 M2 RC1] nettle ptest failure

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13155





[5] Bug 13154 - [2.7 
M2 RC1] perl ptest failure

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13154





Previous Bugs observed in this release:



[6] Bug 13102 - [Bug][QA 2.7 M1 rc1][Toaster] All layers are not getting 
populated after clicking "View compatible layers" on project page

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13102



[7] Bug 13103 - [Bug][QA 2.7 M1 rc1][Toaster] "Recipes" table  and  "machines" 
table are not getting populated after clicking on imported layer as well as 
after clicking Machines Tab on project page

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13103



[8] Bug 13104 - [Bug][QA 2.7 M1 rc1][Toaster] All "Image Recipes" are not 
getting populated after clicking  "Image Recipes"  on project page

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13104



[9] Bug 12991 - [Bug] 
[2.6 M4 RC1][Build-Appliance] Bitbake build-appliance-image getting failed 
during building image due to webkitgtk package.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991



[10] Bug 12499 - [Bug] 
[2.5 M1 RC3] qemuarm: failed to shutdown.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12499






Thanks & Regards,
Sangeeta Jain
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Bitbake Issue in Yocto 2.7 M2 rc1:

[Jain, Sangeeta]

I also faced this issue in current release. For me complete error message is:


ERROR:  OE-core's config sanity checker detected a potential misconfiguration.

Either fix the cause of this error or at your own risk disable the checker 
(see sanity.conf).

Following is the list of potential problems / advisories:



maximum recursion depth exceeded while calling a Python object.

Please ensure your host's network is configured correctly,

or set BB_NO_NETWORK = "1" to disable network access if

all required sources are on local disk.


What worked for me is to disable the network by:
Export BB_NO_NETWORK = "1"

And then re-enable it by

Export BB_NO_NETWORK = "0"

Though not sure of source of this error.


Thanks & Regards,
Sangeeta Jain

From: yocto-boun...@yoctoproject.org  On Behalf 
Of pawanKumar
Sent: Monday, 28 January, 2019 3:04 PM
To: yocto@yoctoproject.org; p...@yoctoproject.org
Subject: [yocto] Bitbake Issue in Yocto 2.7 M2 rc1:

Hi Team,

While running bitbake command, I'm facing issue as:
Error: OE-cores config sanity checker detected a potential misconfiguaration.
Either fix the cause of this error or at your own risk disable the checker (see 
sanity.conf)

Does the issue is in the build or in my system.(I have run in multiple systems)


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA cycle report for 2.6.1 RC1

[Jain, Sangeeta]

Hello All,



This is the full report for 2.6.1 RC1:



https://wiki.yoctoproject.org/wiki/WW02_-_2019-01-09_-_Full_Test_Cycle_2.6.1_RC1





=== Summary 



All planned tests were executed.

Total Test Executed - 3650

Passed Test - 3422

Failed Test - 210

Blocked Test - 12





There were zero high milestone defect.  Team had found 1 new defects coming 
from missing package 'gpg' [1].



For ptest, team had confirmed that there were no tests which passed in 2.6 M4 
while failed in current 2.6.1 rc1. Issues in qa-tools/ptest-parser script used 
to generate comparison table is fixed and script is now working fine.





=== QA-Hints



No high milestone defect.
One of the SDK test cases "/poky/meta/lib/oeqa/sdk/cases/python.py", while 
executed, is giving a result "unknown". We are not sure about the reason of 
this behavior and investigating more into it. This test case is a part of seven 
ADT test plans.



=== Bugs 



New Bugs

[1] Bug 13143 - [Bug] [2.6.1 rc1] bitbake core-image-minimal failed because no 
module named 'gpg' on CentOS 7 and OpenSuse 42.3

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13143



Previous Bugs observed in this release:



[2] Bug 13102 - [Bug][QA 2.7 M1 rc1][Toaster] All layers are not getting 
populated after clicking "View compatible layers" on project page

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13102



[3] Bug 13103 - [Bug][QA 2.7 M1 rc1][Toaster] "Recipes" table  and  "machines" 
table are not getting populated after clicking on imported layer as well as 
after clicking Machines Tab on project page

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13103



[4] Bug 13104 - [Bug][QA 2.7 M1 rc1][Toaster] All "Image Recipes" are not 
getting populated after clicking  "Image Recipes"  on project page

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13104



[5] Bug 12991 - [Bug] 
[2.6 M4 RC1][Build-Appliance] Bitbake build-appliance-image getting failed 
during building image due to webkitgtk package.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991



[6] Bug 12499 - [Bug] 
[2.5 M1 RC3] qemuarm: failed to shutdown.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12499




Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA cycle report for 2.5.2 RC1

[Jain, Sangeeta]

Hello All,



This is the full report for 2.5.2 RC1:

https://wiki.yoctoproject.org/wiki/WW49_-_2018-12-06-_Full_Test_Cycle_-_2.5.2_rc1





Summary



All planned tests were executed.



Total Test Executed - 3389

Passed Test - 3374

Failed Test - 10

Blocked Test - 5



Team had found no new defects.

Test cases failing because of bugs which are not new.



ptest



ptest for 3 module failed in current release but passed in previous 2.5.1 rc1.  
Present status of bugs for respective modules is as follows:



ModuleName  -  BugId  -  Present Status



perl- https://bugzilla.yoctoproject.org/show_bug.cgi?id=13075  - New

python - https://bugzilla.yoctoproject.org/show_bug.cgi?id=13076 - Resolved

tcl - https://bugzilla.yoctoproject.org/show_bug.cgi?id=13077 - New





Performance test



 rootfs performance on ubuntu1604 upgraded by 11.65% in 2.5.2 RC1 w.r.t. 
2.5.1RC1.





QA-Hints



For Bug id 12914, https://bugzilla.yoctoproject.org/show_bug.cgi?id=12914

Regression on previous release and further investigation is in progress to 
confirm the issue





Bugs (Not New)



[1] Bug 12991 -  [2.6 M4 RC1][Build-Appliance] Bitbake build-appliance-image 
getting failed during building image due to webkitgtk package

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991



 [2] Bug 12499 - [2.5 
M1 RC3] qemuarm: failed to shutdown

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12499


[3] Bug 12666 - [2.5 
M3 RC1] BSP-QEMU:core-image-sato-sdk-genericx86-64.hddimg unable to connect to 
console  with serial on Minnowboard Turbot
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12666

[4] Bug 12914 - [2.6 
M2 RC1][Meta-Intel 10.0][NUC7 & Mturbot][Test case 197] reboot command missing 
while installing image
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12914

Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA cycle report for 2.4.4 RC1

[Jain, Sangeeta]

>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Tuesday, 4 December, 2018 11:57 PM
>To: Jain, Sangeeta ; Jolley, Stephen K
>; Eggleton, Paul ;
>Graydon, Tracy ; Erway, Tracey M
>; yocto@yoctoproject.org
>Cc: Sangal, Apoorv ; Kirkiris, Nectar
>
>Subject: Re: QA cycle report for 2.4.4 RC1
>
>On Wed, 2018-11-28 at 07:07 +, Jain, Sangeeta wrote:
>> The test cases run for 2.4.4 RC1 are same as run for 2.4 release.
>
>Ok, but I'm not sure they're correct. Are the test cases we're talking about 
>also
>run for the 2.5 release? I'll explain more below.
>
For 2.5 dot release, we'll run the test cases which we run for 2.5 master 
release.
>> > Thanks for running the QA for this. I do have some
>> > questions/observations.
>> >
>> > Firstly, this report is a little misleading as there are only two
>> > bugs mentioned but 8 failures. The full report shows other bugs
>> > which were for example reopened or already open.
>> In report, only new bugs are mentioned. All the bugs which are
>> reopened/already existing are not listed in report mail but can be
>> seen in full report.
>> However, if its creating any confusion/inconvenience, going forward I
>> can mention all the failing bugs in report.
>
>I think it would be useful to have a complete summary of the bugs found, in
>particular the reopened ones as otherwise it gives a misleading view of the
>release status.
>
Sure.
>> > Taking the above bugs first, I believe they're both manual versions
>> > of tests which are already automated. I believe the automated tests
>> > have passed and there appears to be some kind of problem with the
>> > manual execution such as the wrong process being documented. I'm not
>> > quite sure why these are being run manually? Was the list of manual
>> > tests we received from Intel incorrect?
>> The list manual test we run for 2.4.4 is same as we run for 2.4
>> release. This test case is automated later than 2.4 release and is
>> still manual as per 2.4 test plan in Testopia. It's an irony that in
>> Yocto Project we don't have any tracking of a test case converting
>> into automated in which release, and no system that we can update test
>> cases in Dot releases. I am trying to streamline the tracking of test
>> case evolution, so as to avoid such scenarios in future.
>
>Taking:
>
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=13033
>
>as an example, I believe the automated version is:
>
>http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/lib/oeqa/selftest/cases/prse
>rvice.py?h=rocko#n52
>
>which was present in the first 2.4 release.
>
>Its also present in pyro:
>
>http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/lib/oeqa/selftest/prservice.
>py?h=pyro#n54
>
>and morty:
>http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/lib/oeqa/selftest/prservice.
>py?h=morty#n51
>krogoth:
>http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/lib/oeqa/selftest/prservice.
>py?h=krogoth#n52
>jethro:
>http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/lib/oeqa/selftest/prservice.
>py?h=jethro#n51
>
>so has been there since at least 2.0.
>
>So either I'm wrong about this being an automated version of the test, or we
>really shouldn't be running this test manually but it isn't a problem of 
>changing
>test criteria between point releases.
>
>I'd also note that nobody from QA has replied to my question in the bugzilla.
>
For
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13033
 test case has been run manually for 2.4 release as per Testopia data. 
To answer your question in Bugzilla, we are working on it and will be updated 
asap.

>I'm now worrying about what test cases get run for 2.5 and how these differ 
>from
>what we run against 2.6 and master and what QA summarised in the recent
>documentation of test cases exercise. Perhaps we need to document the manual
>test cases in the 2.5 release too to ensure we have the right set?

 I am working on identifying the test cases which were automated in 2.6 and 
master. And the new test case document summarised by QA team should be aligned 
to latest state of test case, automated or manual.
I am also working on documentation of manual test cases for 2.5 and finding 
which ones are already automated in 2.6, so that we can execute the latest 
state in next release.

>
>Cheers,
>
>Richard


Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA cycle report for 2.4.4 RC1

[Jain, Sangeeta]

The test cases run for 2.4.4 RC1 are same as run for 2.4 release. 


>-Original Message-
>From: richard.pur...@linuxfoundation.org 
>Sent: Saturday, 24 November, 2018 12:07 AM
>To: Jain, Sangeeta ; Jolley, Stephen K
>; Eggleton, Paul ;
>Graydon, Tracy ; Erway, Tracey M
>; yocto@yoctoproject.org
>Cc: Sangal, Apoorv ; Kirkiris, Nectar
>
>Subject: Re: QA cycle report for 2.4.4 RC1
>
>On Fri, 2018-11-23 at 03:23 +, Jain, Sangeeta wrote:
>>
>> Hello All,
>>
>> This is the full report for 2.4.4 RC1:
>>
>https://wiki.yoctoproject.org/wiki/WW46_-_2018-11-14_-
>_Full_Test_Cycle_2.4.4_RC1
>>
>>
>> Summary
>>
>> All planned tests were executed.
>>
>> Total Test Executed – 3330
>> Passed Test – 3318
>> Failed Test – 8
>> Blocked Test - 4
>>
>> There were zero high priority defect.  Team had found 2 new defects.
>>
>> New Bugs
>>
>> [1] Bug 13033 -  [2.4.4RC1] [Bitbake] [Case 142] PR number is not
>> getting increased with remote server/local client mode
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13033
>>
>>  [2]Bug 13038 - [2.4.4RC1][Package Management][Getting Error Message
>> "Failed to synchronize cache for repo 'repository'"]
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13038
>
>Thanks for running the QA for this. I do have some questions/observations.
>
>Firstly, this report is a little misleading as there are only two bugs 
>mentioned but 8
>failures. The full report shows other bugs which were for example reopened or
>already open.
In report, only new bugs are mentioned. All the bugs which are reopened/already 
existing are not listed in report mail but can be seen in full report.
However, if its creating any confusion/inconvenience, going forward I can 
mention all the failing bugs in report.

>
>Taking the above bugs first, I believe they're both manual versions of tests 
>which
>are already automated. I believe the automated tests have passed and there
>appears to be some kind of problem with the manual execution such as the
>wrong process being documented. I'm not quite sure why these are being run
>manually? Was the list of manual tests we received from Intel incorrect?
The list manual test we run for 2.4.4 is same as we run for 2.4 release. This 
test case is automated later than 2.4 release and is still manual as per 2.4 
test plan in Testopia. It's an irony that in Yocto Project we don't have any 
tracking of a test case converting into automated in which release, and no 
system that we can update test cases in Dot releases. I am trying to streamline 
the tracking of test case evolution, so as to avoid such scenarios in future.


>
>Looking at other bugs in the QA report:
>
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=12670
>
>It was reopened as it had been fixed in sumo onwards but not rocko.
>I've backported the fix to the rocko branch. I don't believe its a release 
>blocker.
>
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991
>
>This is webkitgtk failing to build in the build-appliance and looks entirely 
>related
>to resources in the VM. How this could have worked in the past yet fail now
>makes me wonder about whether it was in fact tested previously, whether the
>VM configuration changed or quite what happened. I don't believe its a blocking
>bug as it does seem to be a VM resource problem, not a real failure or problem
>with build-appliance.
>Its hard to tell for sure with the limited data we have though.
>
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=12240
>
>A reopened lsb testing bug but its not really showing problems with the actual
>image, just testing difficulties.
>
>
>Based on this, I think 2.4.4 is good to be released, I don't see any blocking 
>issues.
>I would like to understand what tests are actually being run and why though.
>
>Cheers,
>
>Richard
>
Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA cycle report for 2.4.4 RC1

[Jain, Sangeeta]

Hello All,



This is the full report for 2.4.4 RC1:

https://wiki.yoctoproject.org/wiki/WW46_-_2018-11-14_-_Full_Test_Cycle_2.4.4_RC1





Summary



All planned tests were executed.



Total Test Executed - 3330

Passed Test - 3318

Failed Test - 8

Blocked Test - 4



There were zero high priority defect.  Team had found 2 new defects.



New Bugs



[1] Bug 13033 -  [2.4.4RC1] [Bitbake] [Case 142] PR number is not getting 
increased with remote server/local client mode

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13033



 [2]Bug 13038 - [2.4.4RC1][Package Management][Getting Error Message "Failed to 
synchronize cache for repo 'repository'"]

https://bugzilla.yoctoproject.org/show_bug.cgi?id=13038



Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA cycle report for 2.6 M4 RC1

[Jain, Sangeeta]

Hello All,



This is the full report for 2.6 M4 RC1:

https://wiki.yoctoproject.org/wiki/WW44_-_2018-10-30_-_Full_Test_Cycle_2.6_M4_RC1





Summary



All planned tests were executed.



Total Test Executed - 3339

Passed Test - 3322

Failed Test - 7

Blocked Test - 4



There were zero high priority defect.  Team had found 4 new defects.

ptest for 1 module failed in current release but passed in previous 2.6 M3 rc1. 
 For Openssl no test was executed in current release as well as previous 
release. Present status of bugs for respective modules is as  follows:



ModuleName  -  BugId  -  Present Status



gstreamer- 12990 - New



Note: For busybox, pass rate is lower than previous release, but no test cases 
which passes in previous release failed in current release. Lower pass rate is 
due to new test cases added in this release. No bug filed.



Performance test



 rootfs performance on ubuntu1604 upgraded by  13.04% in 2.6 M3 RC1 w.r.t. 2.6 
M2 RC1



QA-Hints



For performance test, in this release, QA team has performed analysis on 
results from "yocto-perf" mailing list, rather than on results from Linux 
foundation machines.
We observed two major difference between machines used to run Performance test 
by "yocto-perf" mailing list and Linux Foundation machines:

1) Mailing List data points was not constant, sometime more, sometime less
2) Mailing List used machine with different spec



New Bugs



[1] Bug 12974 -  [2.6 M4 RC1] [OE-Core] Crosstap doesn't work on 2.6 M4 RC1

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12974



 [2] Bug 12979 - [2.6 
M4 rc1] test_recipetool_create_cmake failed on Fedora 27

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12979


[3] Bug 12991 - [2.6 
M4 RC1][Build-Appliance] Bitbake build-appliance-image getting failed during 
building image due to webkitgtk package
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12991

[4] Bug 12992 - [2.6 
M4 rc1] test_devtool_add_fetch_git failed on Fedora 27
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12992

Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA cycle report for 2.6 M3 RC1

[Jain, Sangeeta]

Hello All,



This is the full report for 2.6 M3 RC1:

https://wiki.yoctoproject.org/wiki/WW41_-_2018-10-03_-_Full_Test_Cycle_2.6_M3_RC1





Summary



All planned tests were executed.



Total Test Executed - 3358

Passed Test - 3332

Failed Test - 20

Blocked Test - 6



There were zero high priority defect.  Team had found 5 new defects. ptest for 
8 modules failed in current release but passed in previous 2.6 M1 rc1.  Present 
status of bugs for respective modules is as  follows:



ModuleName  -  BugId  -  Present Status



e2fsprogs- 12946 - Accepted, in discussion

gdbm  - 12954 - New

glib-2.0  - 12851 - Won't fix

pango- 12947 - Fixed

perl- 12787  - Accepted for previous release; Failures 
observed in current release also

python  - 12788 - Fixed

strace   - 12948 - New

valgrind   - 12837  - New (Bug is open since 2.6 M1)



Performance test :  rootfs performance on ubuntu1604 degraded by  11.05% in 2.6 
M3 RC1 w.r.t. 2.6 M2 RC1



QA-Hints



Team has observed in ptest report,  it is showing that "openssl" is not 
executed for current release.

But while analyzing ptest logs, following is mentioned in summary for openssl:

Test Summary Report

---

../test/recipes/01-test_symbol_presence.t(Wstat: 512 Tests: 4 Failed: 2)

  Failed tests:  2, 4

  Non-zero exit status: 2

Files=152, Tests=1360, 71 wallclock secs ( 1.41 usr  0.14 sys + 69.96 cusr 
13.14 csys = 84.65 CPU)

Result: FAIL

END: /usr/lib/openssl/ptest





QA Team is investigating more to reach out the correct status and root cause of 
openssl ptest failures.



New Bugs



[1] Bug 12950 -  
[Yocto-2.6_M3.rc1] [MANUAL_SCRIPTS_OE-Core] [Case 2021] [Cross_tap]semantic 
error: while resolving probe point: identifier 'syscall' at trace_open.stp

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12950



[2] Bug 12952 - [QA 
2.6.M3 rc1 ][BSP/Mturbot] Not able to see login prompt when using serial

https://bugzilla.yoctoproject.org/show_bug.cgi?id=12952


[3] Bug 12946 - [2.6 
M3 RC1] e2fsprogs ptest failed
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12946

[4] Bug 12954 - [2.6 
M3 RC1] gdbm ptest failures
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12954

[5] Bug 12948 - [2.6 
M3 RC1] strace ptest failed
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12948


Thanks & Regards,
Sangeeta Jain

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto