We got a few download failures in the last day. I'm opening a ticket just to track them. bb.data_smart.ExpansionError: Failure expanding variable fetcher_hashes_dummyfunc[vardepvalue], expression was ${@bb.fetch.get_hashvalue(d)} which triggered exception FetchError: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export PATH="/srv/pokybuild/yocto-worker/meta-arm/build/build/tmp/work/armv8-5a-poky-linux/ts-sp-its/git/recipe-sysroot-native/usr/bin/python3-native:/srv/pokybuild/yocto-worker/meta-arm/build/layers/openembedded-core/scripts:/srv/pokybuild/yocto-worker/meta-arm/build/build/tmp/work/armv8-5a-poky-linux/ts-sp-its/git/recipe-sysroot-native/usr/bin/aarch64-poky-linux:/srv/pokybuild/yocto-worker/meta-arm/build/build/tmp/work/armv8-5a-poky-linux/ts-sp-its/git/recipe-sysroot/usr/bin/crossscripts:/srv/pokybuild/yocto-worker/meta-arm/build/build/tmp/work/armv8-5a-poky-linux/ts-sp-its/git/recipe-sysroot-native/usr/sbin:/srv/pokybuild/yocto-worker/meta-arm/build/build/tmp/work/armv8-5a-poky-linux/ts-sp-its/git/recipe-sysroot-native/usr/bin:/srv/pokybuild/yocto-worker/meta-arm/build/build/tmp/work/armv8-5a-poky-linux/ts-sp-its/git/recipe-sysroot-native/sbin:/srv/pokybuild/yocto-worker/meta-arm/build/build/tmp/work/armv8-5a-poky-linux/ts-sp-its/git/recipe-sysroot-native/bin:/srv/pokybuild/yocto-worker/meta-arm/build/layers/bitbake/bin:/srv/pokybuild/yocto-worker/meta-arm/build/build/tmp/hosttools"; export HOME="/srv/pokybuild"; git -c gc.autoDetach=false -c core.pager=cat -c safe.bareRepository=all -c clone.defaultRemoteName=origin ls-remote https://git.trustedfirmware.org/TS/trusted-services.git failed with exit code 128, output: fatal: unable to access 'https://git.trustedfirmware.org/TS/trusted-services.git/': Failed to connect to git.trustedfirmware.org port 443 after 128660 ms: Couldn't connect to server
meta-arm debian12-vk-1 mathieu/master-next completed at 2025-10-24 06:58:49+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2512/steps/13/logs/stdio meta-arm debian12-vk-1 mathieu/master-next completed at 2025-10-24 17:39:00+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2515/steps/13/logs/stdio meta-arm fedora39-vk-1 master completed at 2025-10-25 01:25:45+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2517/steps/13/logs/stdio meta-arm ubuntu2204-vk-3 mathieu/master-next completed at 2025-10-25 11:21:54+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2518/steps/13/logs/stdio meta-arm opensuse155-vk-1 mathieu/master-next completed at 2025-10-27 18:17:57+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/2528/steps/14/logs/stdio
Ross: Why doesn't this bug show on the triage list? Are you filtering out other YP layers?
There's known problems with the infrastucture, I'm now subscribed to the internal ticket. Of course the biggest question is "why does the build hit the git repo at all", and the answer to that is "because a tag name was accidentally used" which I'm now fixing.
Upstream infra is more stable now, and meta-arm doesn't hit the repo on every build too since meta-arm 6fd10047a15bc07d14646b82f0d81613e405cdb5.