We got this error on the autobuilder, I believe this is a new one: 2025-12-16 16:58:25,777 - oe-selftest - INFO - WARNING: groff-native-1.23.0-r0 do_recipe_qa_setscene: Failed to fetch URL file://universal/0d/11/sstate:groff-native:x86_64-linux:1.23.0:r0:x86_64:14:0d112f2bc9a7bef9d83c127247c3a578f117f19698c5b88b5239ff4a66f8603b_recipe_qa.tar.zst;downloadfilename=universal/0d/11/sstate:groff-native:x86_64-linux:1.23.0:r0:x86_64:14:0d112f2bc9a7bef9d83c127247c3a578f117f19698c5b88b5239ff4a66f8603b_recipe_qa.tar.zst, attempting MIRRORS if available 2025-12-16 16:58:25,777 - oe-selftest - INFO - ERROR: groff-native-1.23.0-r0 do_recipe_qa_setscene: Fetcher failure: Unable to find file file://universal/0d/11/sstate:groff-native:x86_64-linux:1.23.0:r0:x86_64:14:0d112f2bc9a7bef9d83c127247c3a578f117f19698c5b88b5239ff4a66f8603b_recipe_qa.tar.zst;downloadfilename=universal/0d/11/sstate:groff-native:x86_64-linux:1.23.0:r0:x86_64:14:0d112f2bc9a7bef9d83c127247c3a578f117f19698c5b88b5239ff4a66f8603b_recipe_qa.tar.zst anywhere to download to /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/sstate/universal/0d/11/sstate:groff-native:x86_64-linux:1.23.0:r0:x86_64:14:0d112f2bc9a7bef9d83c127247c3a578f117f19698c5b88b5239ff4a66f8603b_recipe_qa.tar.zst. The paths that were searched were: 2025-12-16 16:58:25,777 - oe-selftest - INFO - /srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/sstate
reproducible fedora40-vk-2 mathieu/master-next completed at 2025-12-16 16:58:38+00:00 https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20251216-w887__ag https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20251216-w887__ag/bitbake-reproducibleB-extended.log https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/3025/steps/13/logs/stdio
Very odd, only the reproducible build failed. Let's see if this ever happens again.
whinlatter reproducible ubuntu2204-vk-4 https://autobuilder.yoctoproject.org/valkyrie/?#/builders/37/builds/3612
Bulk move of 6.0 Medium bugs to 6.1.
Two occurrences, different sstate recipes, very rare and not seen in months. It is possible this was related to sstate cleanup caused by timestamp updates: https://git.openembedded.org/openembedded-core/commit/?id=5213ca88cbec4e86b50d8da1fe4c300ca8f5de17 https://git.openembedded.org/openembedded-core/commit/?id=cc07895f951140dbbffcf32d3eabf65788cc4d00