Bug 15634 - AB-INT: Remote I/O error
Summary: AB-INT: Remote I/O error
Status: RESOLVED OBSOLETE
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided normal
Target Milestone: 0.0.0
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard: AB-INT
Depends on:
Blocks:
 
Reported: 2024-10-28 13:41 UTC by Mathieu Dubois-Briand
Modified: 2024-10-29 22:56 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Dubois-Briand 2024-10-28 13:41:27 UTC
Probably just a builder issue on Valkyrie. Lots of fails today.

Build aborts with errors such as:
Couldn't obtain the lock /srv/autobuilder/valkyrie.yocto.io/pub/non-release/indexing.lock: [Errno 121] Remote I/O error: '/srv/autobuilder/valkyrie.yocto.io/pub/non-release/indexing.lock'

https://valkyrie.yoctoproject.org/#/builders/104/builds/1786/steps/11/logs/stdio
Comment 2 Mathieu Dubois-Briand 2024-10-28 14:16:13 UTC
meta-mingw ubuntu2410-vk-1
https://valkyrie.yoctoproject.org/#/builders/7/builds/341/steps/12/logs/stdio

reproducible fedora40-vk-1
https://valkyrie.yoctoproject.org/#/builders/37/builds/342/steps/12/logs/stdio

buildtools rocky8-vk-1
https://valkyrie.yoctoproject.org/#/builders/43/builds/329/steps/12/logs/stdio

meta-aws ubuntu2404-vk-2
https://valkyrie.yoctoproject.org/#/builders/14/builds/302/steps/12/logs/stdio

meta-virt debian12-vk-8
https://valkyrie.yoctoproject.org/#/builders/89/builds/302/steps/12/logs/stdio

qemuarm-tc ubuntu2410-vk-1
https://valkyrie.yoctoproject.org/#/builders/42/builds/316/steps/12/logs/stdio

qemuarm64-tc alma8-vk-1
https://valkyrie.yoctoproject.org/#/builders/5/builds/317/steps/13/logs/stdio

qemumips-tc debian12-vk-4
https://valkyrie.yoctoproject.org/#/builders/72/builds/312/steps/12/logs/stdio

qemumips64-tc debian12-vk-2
https://valkyrie.yoctoproject.org/#/builders/21/builds/313/steps/12/logs/stdio

qemuppc-tc debian12-vk-3
https://valkyrie.yoctoproject.org/#/builders/49/builds/313/steps/12/logs/stdio

reproducible debian12-vk-4
https://valkyrie.yoctoproject.org/#/builders/37/builds/343/steps/6/logs/stdio

reproducible fedora41-vk-1
https://valkyrie.yoctoproject.org/#/builders/37/builds/344/steps/12/logs/stdio

reproducible opensuse155-vk-1
https://valkyrie.yoctoproject.org/#/builders/37/builds/347/steps/6/logs/stdio

reproducible debian12-vk-3
https://valkyrie.yoctoproject.org/#/builders/37/builds/348/steps/6/logs/stdio

reproducible ubuntu2404-vk-1
https://valkyrie.yoctoproject.org/#/builders/37/builds/349/steps/12/logs/stdio
Comment 4 Richard Purdie 2024-10-29 22:56:14 UTC
For now we're going to assume this was some kind of NFS glitch, we rebooted the workers and haven;t seen it again as far as I know.