Seen several instances of this error: https://valkyrie.yoctoproject.org//#/builders/82/builds/15 https://valkyrie.yoctoproject.org//#/builders/82/builds/16 ERROR: evolution-data-server-native-3.54.0-r0 do_fetch: The URL: 'https://download.gnome.org/sources//evolution-data-server/3.54/evolution-data-server-3.54.0.tar.xz;name=archive' is not trusted and cannot be used ERROR: evolution-data-server-native-3.54.0-r0 do_fetch: Bitbake Fetcher Error: FetchError('Unable to fetch URL from any source.', 'https://download.gnome.org/sources//evolution-data-server/3.54/evolution-data-server-3.54.0.tar.xz;name=archive') 2024-10-13 02:19:48,975 - oe-selftest - INFO - ====================================================================== 2024-10-13 02:19:48,975 - oe-selftest - INFO - FAIL: test_yocto_source_mirror (buildoptions.SourceMirroring.test_yocto_source_mirror) 2024-10-13 02:19:48,975 - oe-selftest - INFO - ---------------------------------------------------------------------- 2024-10-13 02:19:48,975 - oe-selftest - INFO - Traceback (most recent call last): File "/srv/pokybuild/yocto-worker/meta-oe-mirror/build/meta/lib/oeqa/selftest/cases/buildoptions.py", line 232, in test_yocto_source_mirror bitbake("world --runall fetch") File "/srv/pokybuild/yocto-worker/meta-oe-mirror/build/meta/lib/oeqa/utils/commands.py", line 234, in bitbake return runCmd(cmd, ignore_status, timeout, output_log=output_log, **options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/srv/pokybuild/yocto-worker/meta-oe-mirror/build/meta/lib/oeqa/utils/commands.py", line 212, in runCmd raise AssertionError("Command '%s' returned non-zero exit status %d:\n%s" % (command, result.status, exc_output)) AssertionError: Command 'bitbake world --runall fetch' returned non-zero exit status 1:
RP: Sources are still mirrored off typhoon but we've stopped that cluster and are running off valkyrie. This could mean sources don't appear "fast" in the mirror until that mirroring moves to the new NAS. Who/Plan: Michael to transition mirroring to run of valkyrie NAS
We have completed migration to the new infrastructure and this is now resolved