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

Hello Richard,

We had the same kind of error, we suspect some issue on crates.io side, did
you have any news from them?

I couldn't find anything about this issue.

Shall we change the way we download the crates?

Regards,

Yann CARDAILLAC,
--------------------------------------------------------------------------------------------------------------------



On Fri, Apr 24, 2026 at 2:11 PM Richard Purdie via lists.yoctoproject.org
<[email protected]> wrote:

> On Fri, 2026-04-24 at 08:28 +0000, Pokybuild User via
> lists.yoctoproject.org wrote:
> >
> >     A build flagged for QA (yocto-6.0.rc1) was completed on the
> autobuilder and is available at:
> >
> >
> >         https://valkyrie.yocto.io/pub/releases/yocto-6.0.rc1
> >
> >
> >     Build URL:
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3727
> >
> >     Build hash information:
> >
> >     bitbake: 33581c84f3a85008239acbd940501a35de48dc91
> > meta-agl: 335bfb321925d37675d45f0f869c446ded8972ce
> > meta-arm: 8eb10af8092dc3fff86891339fd024d8583f457f
> > meta-aws: fefdcc67dc3a86752a98d19c96d64bcb31928002
> > meta-clang: 78c5e12f08198f4f257a9348516d2103cd617c1d
> > meta-intel: 511ddb7ea90499b2088248f59bab3e9d6f3c900c
> > meta-mingw: a4ba674d6a0a17e4c0bc4c11bbb9d0ea9de2b315
> > meta-openembedded: 76700b6eaf327bb30e2c47b78713e2e409cfab7c
> > meta-qcom: a9f20e62e569c232dc1aaf8a90a6343e504003ef
> > meta-virtualization: 2e0704ee9282e4e86c13180334cb7ce118e55dd9
> > meta-yocto: 904846ae078ee20de073040ebb77c86e19250f56
> > oecore: 42fa856a00ac16b2a7a83d7ecfa60a5be192b16c
> > yocto-docs: eb74fdfd9e5e579a65e8872d1a73b51e77b14f63
>
> This build did show three issues:
>
> a) A bitbake-selftest fetcher failure with 403 errors from crates.io.
> This is an intermittent network error, probably rate limiting
> connection requests.
>
> b) Some oe-selftest failures from importlib on ubuntu 22.04, where
> importlib fails with a KeyError, this exits whilst holding a lock
> causing other failures though deadlock. I manually killed a process to
> let the rest of the build finish. This is a known issue in older python
> versions.
>
> c) A failure in meta-virtualization from recent changes. There is a
> patch on the mailing list and this will be fixed before release.
>
> I do not believe any of these are release blockers and propose we
> should proceed with QA.
>
> Thanks,
>
> Richard
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#66439):
> https://lists.yoctoproject.org/g/yocto/message/66439
> Mute This Topic: https://lists.yoctoproject.org/mt/118986370/3617030
> Group Owner: [email protected]
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> [email protected]]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>