This happened twice and didn't happen anymore, on master. Tracking it with this bug to see if it happens again: Running '. ./init-build-env; ${SCRIPTSDIR}/generate-testresult-index.py /srv/autobuilder/valkyrie.yocto.io/pub/non-release/' with output to /srv/pokybuild/yocto-worker/indexing/build/build/command-1-cmds.log in /srv/pokybuild/yocto-worker/indexing/build/build Couldn't obtain the lock /srv/autobuilder/valkyrie.yocto.io/pub/non-release/indexing.lock: [Errno 11] Resource temporarily unavailable
indexing alma9-vk-2 master completed at 2026-09-17 09:50:00+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/104/builds/66607/steps/15/logs/stdio indexing alma10-vk-1 master completed at 2026-09-17 09:43:05+00:00 https://autobuilder.yoctoproject.org/valkyrie/#/builders/104/builds/66608/steps/14/logs/stdio
Indexing job likely took too long likely due to load. The NAS has had some problems due to a power failure causing some data corruption. The NAS performance has been degraded as it provides service and fixes the FS state. We don't plan to change this.