RE: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-6.0_M2.rc3)

Hi Paul, everyone.

Sure thing, we will execute & conclude QA executions for yocto-6.0_M2.rc3 before we proceed with yocto-4.0.34. 
The QA-cycle for yocto-5.3.2 has been concluded.

Revised ETA:

yocto-6.0_M2.rc3: 11/03/2026
yocto-4.0.34: 18/03/2026.

Regards,
Debal Ghosh

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Paul Barker
Sent: 03 March 2026 20:25
To: Ghosh, Debal <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; Yocto TSC <[email protected]>
Subject: Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-6.0_M2.rc3)

On Mon, 2026-03-02 at 15:19 +0000, Richard Purdie via lists.yoctoproject.org wrote:
> On Mon, 2026-03-02 at 11:38 +0000, Pokybuild User via lists.yoctoproject.org wrote:
> > 
> >     A build flagged for QA (yocto-6.0_M2.rc3) was completed on the autobuilder and is available at:
> > 
> >         https://valkyrie.yocto.io/pub/releases/yocto-6.0_M2.rc3
> > 
> > 
> >     Build URL: 
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3
> > 316
> > 
> >     Build hash information: 
> > 
> >     bitbake: bc8be83aef0a6de85cd33a6f132f281d518594f7
> > meta-agl: c1761e898d7fca3d8438e9b010eaf234f94fa407
> > meta-arm: b00fe8862bc31cd4b6f0299b6a2edb244f19487a
> > meta-aws: b570577bf3ae3752e27bac15faf8733e45a01360
> > meta-clang: cf20f8bd1366d41094c945597b95dd746e87b871
> > meta-intel: b6c23896d3eee0f925cbe189ff1e67b3c4953353
> > meta-mingw: 11666fce6a3cc98bcff6fe2c6bdd9e48faf03767
> > meta-openembedded: 6ba45c1f94e1c2015df940ec9efcd4568346df56
> > meta-qcom: 1a7b6b0363fa75232d46ffb9fd706b9539872e10
> > meta-virtualization: 506d5af230f0b41809dfe754e84d5611b75c6585
> > meta-yocto: f3b63d0d6882af61020bd6f7150fae68a0322f63
> > oecore: be8cdcf13a658e9e81ff2f7b71d1c8c37a920ce7
> > yocto-docs: d97cfeaa55ed42722998d3313c1857aa377f6881

Hi Debal,

The TSC discussed 6.0 M2 yesterday and are happy that Richard's concerns below should not block QA or release of this milestone.

Please prioritise 6.0 M2 for QA, ahead of 5.3.2 and 4.0.34 if possible.
Please give us revised ETA dates for those two releases if you're able to test 6.0 M2 first.

> 
> There were two error issues with this build:
> 
> a) A ruby reproducibility issue in the docs package. There is a patch 
> on the mailing list. A v1 of a patch was merged instead of a v2.
> 
> b) A failure with the regression report generation due to confusion 
> about tags.
> 
> As well as some warnings:
> 
> a) python3 ptest failure on qemuarm64
> 
> b) Warning about duplicate includes from meta-agl-core
> 
> c) warning about fedora-43 not being a supported host (patch now 
> merged to fix)
> 
> 
> Since two issues have fixes ready or merged, one is easily fixed, and 
> the python3 ptest issue is known, that leaves the regression report 
> issue. That will need more investigation/work but I don't believe any 
> of these should further block M2 from entering QA.
> 
> Cheers,
> 
> Richard

Best regards,

--
Paul Barker