QA notification for completed autobuilder build (yocto-5.0.rc2)

QA notification for completed autobuilder build (yocto-5.0.rc2)

[Pokybuild User]

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


        https://autobuilder.yocto.io/pub/releases/yocto-5.0.rc2


    Build URL: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6813

    Build hash information: 

    bitbake: c86466d51e8ff14e57a734c1eec5bb651fdc73ef
meta-agl: 8c5e4a89bd4d9436e9ba929bd0faaf32744f6a64
meta-arm: 04187be11dc4bfc898d411c1a40c2a1e9f4ff925
meta-aws: 216c095de9d546c141a90017a91a3ccb226de754
meta-clang: 989ff6a4e7db59f01d511727135610006124ead2
meta-intel: 0e43ce8605006b941cdfdab1f2112c5afc8e4663
meta-mingw: d1df6908922a5357c408be77ff18f812e9e999af
meta-openembedded: a7c8ce7f674008db4d7013557ec375a35226f43f
meta-virtualization: b7e77b69d309d8ee985720e88b19b6e9cf03fe63
oecore: 09ccab7d0b4d815b812e49a5861a13a4ec0189b9
poky: 5b727a8fa1acfa9eeb441ac835ca7d24099284a9


    
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-5.0.rc2)

[Richard Purdie]

On Wed, 2024-04-17 at 08:37 +0000, Pokybuild User via lists.yoctoproject.org wrote:
> 
>     A build flagged for QA (yocto-5.0.rc2) was completed on the autobuilder and is available at:
> 
> 
>         https://autobuilder.yocto.io/pub/releases/yocto-5.0.rc2
> 
> 
>     Build URL: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6813

This does have two failures in it and two known ptest warnings (curl and gstreamer).

The failures are from:

a) a github network issue (rate limiting?)

b) pip being missing in the buildtools tarball used to run the build for patchtest-selftest

For b), updating buildtools should resolve it, I thought I had done
that but there were a lot of moving pieces so I must not have got the
latest.

I'm proposing we do but this into QA as I'd not block release on these
issues. I've done my best to get this into as good a shape as we can.

Cheers,

Richard

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

[Ross Burton]

On 17 Apr 2024, at 09:50, Richard Purdie via lists.yoctoproject.org <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote:
> For b), updating buildtools should resolve it, I thought I had done
> that but there were a lot of moving pieces so I must not have got the
> latest.
> 
> I'm proposing we do but this into QA as I'd not block release on these
> issues. I've done my best to get this into as good a shape as we can.

Agreed.  Can we do a build in the meantime of the specific job that failed so we can verify the buildtools/pip issue is resolved?

Ross

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

[Denys Dmytriyenko]

On Wed, Apr 17, 2024 at 11:36:27AM +0000, Ross Burton wrote:
> On 17 Apr 2024, at 09:50, Richard Purdie via lists.yoctoproject.org <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote:
> > For b), updating buildtools should resolve it, I thought I had done
> > that but there were a lot of moving pieces so I must not have got the
> > latest.
> > 
> > I'm proposing we do but this into QA as I'd not block release on these
> > issues. I've done my best to get this into as good a shape as we can.
> 
> Agreed.  Can we do a build in the meantime of the specific job that failed 
> so we can verify the buildtools/pip issue is resolved?

Sounds reasonable.

-- 
Denys

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

[Khem Raj]

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

On Wed, Apr 17, 2024 at 1:50 AM Richard Purdie via lists.yoctoproject.org
<richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote:

> On Wed, 2024-04-17 at 08:37 +0000, Pokybuild User via
> lists.yoctoproject.org wrote:
> >
> >     A build flagged for QA (yocto-5.0.rc2) was completed on the
> autobuilder and is available at:
> >
> >
> >         https://autobuilder.yocto.io/pub/releases/yocto-5.0.rc2
> >
> >
> >     Build URL:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6813
>
> This does have two failures in it and two known ptest warnings (curl and
> gstreamer).
>
> The failures are from:
>
> a) a github network issue (rate limiting?)


Do we know it works ok in another build ?

>
>
> b) pip being missing in the buildtools tarball used to run the build for
> patchtest-selftest
>
> For b), updating buildtools should resolve it, I thought I had done
> that but there were a lot of moving pieces so I must not have got the
> latest.
>
> I'm proposing we do but this into QA as I'd not block release on these
> issues. I've done my best to get this into as good a shape as we can.
>

I am ok with this going ahead


> Cheers,
>
> Richard
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#2031):
> https://lists.yoctoproject.org/g/tsc/message/2031
> Mute This Topic: https://lists.yoctoproject.org/mt/105573382/1997914
> Group Owner: tsc+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/tsc/unsub [
> raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

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

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

[Richard Purdie]

On Wed, 2024-04-17 at 11:36 +0000, Ross Burton via
lists.yoctoproject.org wrote:
> On 17 Apr 2024, at 09:50, Richard Purdie via lists.yoctoproject.org
> <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote:
> > For b), updating buildtools should resolve it, I thought I had done
> > that but there were a lot of moving pieces so I must not have got
> > the
> > latest.
> > 
> > I'm proposing we do but this into QA as I'd not block release on
> > these
> > issues. I've done my best to get this into as good a shape as we
> > can.
> 
> Agreed.  Can we do a build in the meantime of the specific job that
> failed so we can verify the buildtools/pip issue is resolved?

I dug into the "github failure" and it turns out that if you have git
2.44.0 compiled/linked against curl 8.7.1 then the command:

git-clone --bare --mirror https://github.com/grpc/grpc.git /tmp/somewhere

exits silently with an error exit code of 141 (SIGPIPE).

With curl 8.6.0 this doesn't happen and the new buildtools has the new
curl+git version.

You can demo this in a build quite simply with:

$ bitbake git-replacement-native -c compile

then:

$ PATH=./tmp/work/aarch64-linux/git-native/2.44.0/git-2.44.0/:$PATH git-clone --bare --mirror https://github.com/grpc/grpc.git /tmp/bitbake-fetch-test

More digging to do to debug it but that should be enough to let others
reproduce. I suspect it will happen on x86 too, I just used the arm
worker to narrow it down since it was the most frequent occurrence.

You have to manipulate PATH so git's internal exec calls find the right
git binaries. We'll not mention how it took me to work that out.

Cheers,

Richard

RE: [qa-build-notification] QA notification for completed autobuilder build (yocto-5.0.rc2)

[Tham, Jing Hui]

Hi all,
 
Intel and WR YP QA is planning for QA execution for YP build yocto-5.0.rc2. 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. MinnowBoard Turbot - 32bit
	2. Alder Lake-S (12th Generation Intel(r) Core(tm) Processors)
	3. Raptor Lake-P (13th Generation Intel(r) Core(tm) Processors)
	4. Meteor Lake-P (14th Generation Intel(r) Core(tm) Processors)
	5. Beaglebone
 
 
ETA for completion next Tuesday, 23 April.
 
Best regards,
Jing Hui

> -----Original Message-----
> From: qa-build-notification@lists.yoctoproject.org <qa-build-
> notification@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Wednesday, April 17, 2024 4:37 PM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notification@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-5.0.rc2)
> 
> 
>     A build flagged for QA (yocto-5.0.rc2) was completed on the autobuilder
> and is available at:
> 
> 
>         https://autobuilder.yocto.io/pub/releases/yocto-5.0.rc2
> 
> 
>     Build URL:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6813
> 
>     Build hash information:
> 
>     bitbake: c86466d51e8ff14e57a734c1eec5bb651fdc73ef
> meta-agl: 8c5e4a89bd4d9436e9ba929bd0faaf32744f6a64
> meta-arm: 04187be11dc4bfc898d411c1a40c2a1e9f4ff925
> meta-aws: 216c095de9d546c141a90017a91a3ccb226de754
> meta-clang: 989ff6a4e7db59f01d511727135610006124ead2
> meta-intel: 0e43ce8605006b941cdfdab1f2112c5afc8e4663
> meta-mingw: d1df6908922a5357c408be77ff18f812e9e999af
> meta-openembedded: a7c8ce7f674008db4d7013557ec375a35226f43f
> meta-virtualization: b7e77b69d309d8ee985720e88b19b6e9cf03fe63
> oecore: 09ccab7d0b4d815b812e49a5861a13a4ec0189b9
> poky: 5b727a8fa1acfa9eeb441ac835ca7d24099284a9
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.purdie@linuxfoundation.org
> 
> 
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#406): https://lists.yoctoproject.org/g/qa-build-
> notification/message/406
> Mute This Topic: https://lists.yoctoproject.org/mt/105573316/6424044
> Group Owner: qa-build-notification+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/qa-build-
> notification/leave/10762429/6424044/1746813897/xyzzy
> [jing.hui.tham@intel.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

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

[Richard Purdie]

On Wed, 2024-04-17 at 22:23 +0100, Richard Purdie via lists.yoctoproject.org wrote:
> On Wed, 2024-04-17 at 11:36 +0000, Ross Burton via
> lists.yoctoproject.org wrote:
> > On 17 Apr 2024, at 09:50, Richard Purdie via lists.yoctoproject.org
> > <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote:
> > > For b), updating buildtools should resolve it, I thought I had done
> > > that but there were a lot of moving pieces so I must not have got
> > > the
> > > latest.
> > > 
> > > I'm proposing we do but this into QA as I'd not block release on
> > > these
> > > issues. I've done my best to get this into as good a shape as we
> > > can.
> > 
> > Agreed.  Can we do a build in the meantime of the specific job that
> > failed so we can verify the buildtools/pip issue is resolved?
> 
> I dug into the "github failure" and it turns out that if you have git
> 2.44.0 compiled/linked against curl 8.7.1 then the command:
> 
> git-clone --bare --mirror https://github.com/grpc/grpc.git /tmp/somewhere
> 
> exits silently with an error exit code of 141 (SIGPIPE).
> 
> With curl 8.6.0 this doesn't happen and the new buildtools has the new
> curl+git version.
> 
> You can demo this in a build quite simply with:
> 
> $ bitbake git-replacement-native -c compile
> 
> then:
> 
> $ PATH=./tmp/work/aarch64-linux/git-native/2.44.0/git-2.44.0/:$PATH git-clone --bare --mirror https://github.com/grpc/grpc.git /tmp/bitbake-fetch-test
> 
> More digging to do to debug it but that should be enough to let others
> reproduce. I suspect it will happen on x86 too, I just used the arm
> worker to narrow it down since it was the most frequent occurrence.
> 
> You have to manipulate PATH so git's internal exec calls find the right
> git binaries. We'll not mention how it took me to work that out.

For the purposes of history, the issue is in curl 8.7.0 and 8.7.1 was
just a single bug fix. There is a fix in git master branch for the curl
issue and curl themselves also have a fix in master as yet unreleased.
I've backported the patch to git for now, we can drop it when we
upgrade things.

Cheers,

Richard

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

[Richard Purdie]

On Thu, 2024-04-18 at 10:45 +0000, Ross Burton wrote:
> On 18 Apr 2024, at 09:11, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > For the purposes of history, the issue is in curl 8.7.0 and 8.7.1 was
> > just a single bug fix. There is a fix in git master branch for the curl
> > issue and curl themselves also have a fix in master as yet unreleased.
> > I've backported the patch to git for now, we can drop it when we
> > upgrade things.
> 
> As the underlying issue is in curl and has been fixed in master:
> 
> https://github.com/curl/curl/commit/721941aadf4adf4f6aeb3f4c0ab489bb89610c36
> 
> I think we should apply this instead.  The issue is a curl regression, we just saw it first in git.
> 
> I lean towards this being a release blocker and think we should respin.

Much as I would prefer not to, I agree. 

We should abandon rc2 and build an rc3. I'd like to keep the
dunfell/kirkstone builds for after rc3 goes through QA though. We
should be able to build rc3 quite quickly.

Cheers,

Richard

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

[Denys Dmytriyenko]

On Thu, Apr 18, 2024 at 11:49:26AM +0100, Richard Purdie wrote:
> On Thu, 2024-04-18 at 10:45 +0000, Ross Burton wrote:
> > On 18 Apr 2024, at 09:11, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > > For the purposes of history, the issue is in curl 8.7.0 and 8.7.1 was
> > > just a single bug fix. There is a fix in git master branch for the curl
> > > issue and curl themselves also have a fix in master as yet unreleased.
> > > I've backported the patch to git for now, we can drop it when we
> > > upgrade things.
> > 
> > As the underlying issue is in curl and has been fixed in master:
> > 
> > https://github.com/curl/curl/commit/721941aadf4adf4f6aeb3f4c0ab489bb89610c36
> > 
> > I think we should apply this instead.  The issue is a curl regression, we just saw it first in git.
> > 
> > I lean towards this being a release blocker and think we should respin.
> 
> Much as I would prefer not to, I agree. 
> 
> We should abandon rc2 and build an rc3. I'd like to keep the
> dunfell/kirkstone builds for after rc3 goes through QA though. We
> should be able to build rc3 quite quickly.

I believe 5.0 is still "within" the schedule, right?

What about dunfell and kirkstone minor releases? I know their builds are being 
delayed by 5.0 taking up AB. But are they already behind the schedule? If not, 
then 5.0 rc3 should definitely get prioritized.

-- 
Denys

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

[Richard Purdie]

On Thu, 2024-04-18 at 11:45 -0400, Denys Dmytriyenko wrote:
> On Thu, Apr 18, 2024 at 11:49:26AM +0100, Richard Purdie wrote:
> > On Thu, 2024-04-18 at 10:45 +0000, Ross Burton wrote:
> > > On 18 Apr 2024, at 09:11, Richard Purdie
> > > <richard.purdie@linuxfoundation.org> wrote:
> > > > For the purposes of history, the issue is in curl 8.7.0 and
> > > > 8.7.1 was
> > > > just a single bug fix. There is a fix in git master branch for
> > > > the curl
> > > > issue and curl themselves also have a fix in master as yet
> > > > unreleased.
> > > > I've backported the patch to git for now, we can drop it when
> > > > we
> > > > upgrade things.
> > > 
> > > As the underlying issue is in curl and has been fixed in master:
> > > 
> > > https://github.com/curl/curl/commit/721941aadf4adf4f6aeb3f4c0ab489bb89610c36
> > > 
> > > I think we should apply this instead.  The issue is a curl
> > > regression, we just saw it first in git.
> > > 
> > > I lean towards this being a release blocker and think we should
> > > respin.
> > 
> > Much as I would prefer not to, I agree. 
> > 
> > We should abandon rc2 and build an rc3. I'd like to keep the
> > dunfell/kirkstone builds for after rc3 goes through QA though. We
> > should be able to build rc3 quite quickly.
> 
> I believe 5.0 is still "within" the schedule, right?
> 
> What about dunfell and kirkstone minor releases? I know their builds
> are being delayed by 5.0 taking up AB. But are they already behind
> the schedule? If not, then 5.0 rc3 should definitely get prioritized.

The dunfell build is actually built and ready for QA.

The schedule is ours to run though and I think the correct thing to do
is to get 5.0 rc4 into QA, then the others.

I've stopped the rc3 build as there was still a buildtools issue. It
was infrastructure usage related rather than anything in the tarball
this time. rc4 is therefore building. I cancelled a load of master
stuff to ensure it has priority.

Cheers,

Richard