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

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

[Pokybuild User]

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


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


Build hash information: 

bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
poky: eee9fba7b4d5d7a268a495688039027390894e6d



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


 

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

[Richard Purdie]

On Wed, 2022-04-20 at 06:02 +0000, Pokybuild User wrote:
> A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and is available at:
> 
> 
>     https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1
> 
> 
> Build hash information: 
> 
> bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
> meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
> meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
> meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
> meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
> meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
> meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
> meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
> oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
> poky: eee9fba7b4d5d7a268a495688039027390894e6d

3.3.6 built but there were two issues. One was a qemu boot test failure for
core-image-sato-sdk on qemuppc-alt. I did have a look for logs but there aren't
any, qemu never seemed to start but nothing to indicate why. Since the other
tests for ppc passed, I think this is one of our general intermittent problems
on ppc and we should ignore it.

The other was some valgrind ptest failures. Those are known intermittent issues
and I believe also not significant from a release perspective.

Cheers,

Richard

Re: [EXTERNAL] Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

[Raj, Khem]

[-- Attachment #1: Type: text/plain, Size: 2070 bytes --]

Is the sato-sdk on qemuppc also intermittent issue
________________________________
From: tsc@lists.yoctoproject.org <tsc@lists.yoctoproject.org> on behalf of Richard Purdie <richard.purdie@linuxfoundation.org>
Sent: Wednesday, April 20, 2022 12:29:29 AM
To: qa-build-notification@lists.yoctoproject.org <qa-build-notification@lists.yoctoproject.org>; yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org>
Cc: Yocto TSC <tsc@lists.yoctoproject.org>; Mittal, Anuj <anuj.mittal@intel.com>
Subject: [EXTERNAL] Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

On Wed, 2022-04-20 at 06:02 +0000, Pokybuild User wrote:
> A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and is available at:
>
>
>     https://urldefense.com/v3/__https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1__;!!CQl3mcHX2A!XITvSVzpVXHE-hKopFwPzKrqpC-fi6MhLyNlACbodEIHW7S3PBGSenxMWW9GU4pG$
>
>
> Build hash information:
>
> bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
> meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
> meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
> meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
> meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
> meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
> meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
> meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
> oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
> poky: eee9fba7b4d5d7a268a495688039027390894e6d

3.3.6 built but there were two issues. One was a qemu boot test failure for
core-image-sato-sdk on qemuppc-alt. I did have a look for logs but there aren't
any, qemu never seemed to start but nothing to indicate why. Since the other
tests for ppc passed, I think this is one of our general intermittent problems
on ppc and we should ignore it.

The other was some valgrind ptest failures. Those are known intermittent issues
and I believe also not significant from a release perspective.

Cheers,

Richard





[-- Attachment #2: Type: text/html, Size: 3169 bytes --]

Re: [EXTERNAL] Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

[Raj, Khem]

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

OK I would be fine to go with this assertion and perhaps monitor it closely to be classified as intermittent or something one off.

From: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Wednesday, April 20, 2022 at 7:19 AM
To: Raj, Khem <Khem_Raj@cable.comcast.com>, qa-build-notification@lists.yoctoproject.org <qa-build-notification@lists.yoctoproject.org>, yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org>
Cc: Yocto TSC <tsc@lists.yoctoproject.org>, Mittal, Anuj <anuj.mittal@intel.com>
Subject: Re: [EXTERNAL] Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)
On Wed, 2022-04-20 at 14:14 +0000, Raj, Khem wrote:
> Is the sato-sdk on qemuppc also intermittent issue

It doesn't usually happen and works fine in other builds so it is intermittent.
Whether it is one of our "known" intermittent issues, I don't know. I couldn't
get any real information from the system about why it failed. We have better
logging in master.

Cheers,

Richard



[-- Attachment #2: Type: text/html, Size: 2864 bytes --]

RE: [yocto] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

[Teoh, Jay Shen]

Hi all,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.3.6.rc1. We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. NUC 7
3. NUC 6
4. Edgerouter
5. Beaglebone

ETA for completion next Monday, April 25.

Thanks,
Jay

> -----Original Message-----
> From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf
> Of Pokybuild User
> Sent: Wednesday, 20 April, 2022 2:02 PM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notification@lists.yoctoproject.org
> Subject: [yocto] QA notification for completed autobuilder build (yocto-
> 3.3.6.rc1)
> 
> 
> A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder
> and is available at:
> 
> 
>     https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1
> 
> 
> Build hash information:
> 
> bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
> meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
> meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
> meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
> meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
> meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
> meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
> meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
> oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
> poky: eee9fba7b4d5d7a268a495688039027390894e6d
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.purdie@linuxfoundation.org
> 
> 
> 

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

[akuster808]

no issues from me.

-armin

On 4/20/22 00:29, Richard Purdie wrote:
> On Wed, 2022-04-20 at 06:02 +0000, Pokybuild User wrote:
>> A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and is available at:
>>
>>
>>      https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1
>>
>>
>> Build hash information:
>>
>> bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
>> meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
>> meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
>> meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
>> meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
>> meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
>> meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
>> meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
>> oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
>> poky: eee9fba7b4d5d7a268a495688039027390894e6d
> 3.3.6 built but there were two issues. One was a qemu boot test failure for
> core-image-sato-sdk on qemuppc-alt. I did have a look for logs but there aren't
> any, qemu never seemed to start but nothing to indicate why. Since the other
> tests for ppc passed, I think this is one of our general intermittent problems
> on ppc and we should ignore it.
>
> The other was some valgrind ptest failures. Those are known intermittent issues
> and I believe also not significant from a release perspective.
>
> Cheers,
>
> Richard
>
>
>
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#129): https://lists.yoctoproject.org/g/qa-build-notification/message/129
> Mute This Topic: https://lists.yoctoproject.org/mt/90578884/3616698
> Group Owner: qa-build-notification+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/qa-build-notification/leave/8918815/3616698/368265748/xyzzy [akuster808@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

RE: [yocto] QA notification for completed autobuilder build (yocto-3.3.6.rc1)

[Teoh, Jay Shen]

Hello everyone,

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

======= Summary ========
No high milestone defects.

No new issue found.

Thanks,
Jay
> -----Original Message-----
> From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf
> Of Pokybuild User
> Sent: Wednesday, 20 April, 2022 2:02 PM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notification@lists.yoctoproject.org
> Subject: [yocto] QA notification for completed autobuilder build (yocto-
> 3.3.6.rc1)
> 
> 
> A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder
> and is available at:
> 
> 
>     https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1
> 
> 
> Build hash information:
> 
> bitbake: d01d8326331cfe59208674cfc53aa26c0028b313
> meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62
> meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20
> meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58
> meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
> meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d
> meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e
> meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e
> oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
> poky: eee9fba7b4d5d7a268a495688039027390894e6d
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.purdie@linuxfoundation.org
> 
> 
>