Le mer. 21 janv. 2026 à 12:56, Ghosh, Debal via lists.yoctoproject.org <[email protected]> a écrit :
> Hi All, > > QA for Yocto-5.3.1.rc2 is completed. This is the full report for this > release: > > 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, > Debal Ghosh > > ------------------------------ > *From:* [email protected] < > [email protected]> on behalf of Ghosh, Debal > via lists.yoctoproject.org <[email protected]> > *Sent:* Tuesday, January 13, 2026 11:32 AM > *To:* [email protected] < > [email protected]>; Yocto-mailing-list < > [email protected]>; openembedded-core < > [email protected]>; Pokybuild User < > [email protected]> > *Subject:* Re: [qa-build-notification] QA notification for completed > autobuilder build (yocto-5.3.1.rc2) > > Hi all, > > Intel and WR YP QA is planning for QA execution for YP build > Yocto-5.3.1.rc2. We are planning to execute the following tests for this > cycle: > > > OEQA-manual tests for following module: > OE-Core > BSP-hw > > > Runtime auto test for following platforms: > > MinnowBoard Turbot - 32bit > Alder Lake-S > Meteor Lake-P > Arrow lake > Bartlett lake-S > Amston lake > Twin lake > Beaglebone > BeaglePlay > > > > > ETA for completion: 21/01/2026. > > > Best regards, > Debal Ghosh > > -----Original Message----- > From: [email protected] < > [email protected]> On Behalf Of Pokybuild User > via lists.yoctoproject.org > Sent: 13 January 2026 04:38 > To: [email protected] > Cc: [email protected] > Subject: [qa-build-notification] QA notification for completed autobuilder > build (yocto-5.3.1.rc2) > > > A build flagged for QA (yocto-5.3.1.rc2) was completed on the > autobuilder and is available at: > > > https://valkyrie.yocto.io/pub/releases/yocto-5.3.1.rc2 > > > Build URL: > https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3041 > > Hello, There was a mistake in the branches used for some of the non-core repos: for some repos, the master branch was used instead of whinlatter : > Build hash information: > > bitbake: 663021740bc086bd959a8457ad9ddb6da52a8278 > meta-yocto: 6973ca663aaa9c3ab517ee960ab7985a5bf54c07 > oecore: dd10706cfafb5574b7cf316fca2300d166ef71b0 > yocto-docs: 102a33294e63a5581c413555040f790161fc80ff > All of those "Core" repo are OK, the build was on the expected commit from the whinlatter branch. > meta-agl: fcc4176504cd4b5b9d27d20797b11be5330e9f10 > On the "next" branch but that seems expected. (meta-agl does not follow the same branch pattern) > meta-arm: 955b1d8e6921d8e03388c5013dfaebbb0cfc5099 > Problem: this is on master, not whinlatter! > meta-aws: dde608c015c80442356bd180202f955cc9b61267 > Problem: this is on master, not whinlatter! > meta-clang: cf20f8bd1366d41094c945597b95dd746e87b871 > Problem: this is on master, not whinlatter! > meta-intel: 9182026daca13f7efca0bb6ff1eacb039946c476 > Problem: this is on master, not whinlatter! > meta-mingw: 00323de97e397d4f6734ef2191806616989f5e10 > OK: on whinlatter branch meta-openembedded: a4e768dcfae181dd99e39c4286fa0729ca7f4e47 > OK: on whinlatter branch > meta-qcom: dc5f692bff1032c40a19f4ab4cd7eb63afcfaab1 > OK: on master but meta-qcom does not have a whinlatter branch > meta-virtualization: 28d26fd95397bf575e65fcca0cbb302b1e9bc7ff > Problem: this is on master, not whinlatter! I am not sure what should happen now : * Restart the release from scratch with a new a-full -rc build with correct branches used ? * Or, if the QA teams do not use the repos that are on the wrong branch, maybe we can keep the QA results and assemble that with the new -rc a-full build to make this release ? Regards, This is an automated message from the Yocto Project Autobuilder > Git: git://git.yoctoproject.org/yocto-autobuilder2 > Email: [email protected] > > > > > > > > > > > > > > > > -- Yoann Congal Smile ECS
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#229816): https://lists.openembedded.org/g/openembedded-core/message/229816 Mute This Topic: https://lists.openembedded.org/mt/117239477/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
