Bug 15906 - AB-INT: prepare-shared-repos timeout
Summary: AB-INT: prepare-shared-repos timeout
Status: RESOLVED WORKSFORME
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 5.3 M2
Assignee: Michael Halstead
QA Contact:
URL:
Whiteboard: AB-INT
Depends on:
Blocks:
 
Reported: 2025-06-12 12:59 UTC by Mathieu Dubois-Briand
Modified: 2025-08-21 14:52 UTC (History)
6 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 2025-06-12 12:59:47 UTC
Saw this a few times in the last weeks, I ignored the first occurrences but this seems to be more frequent than I previously thought.

====================================================================================================
Initially fetching repo poky (1749715397.9)
====================================================================================================

Checking for stash at: /srv/pokybuild/git/mirror/poky
Cloning from stash to /home/pokybuild/tmp/shared-repo-temp-yljlgrjp/poky...
Cloning into '/home/pokybuild/tmp/shared-repo-temp-yljlgrjp/poky'...
Updating from origin...

command timed out: 1200 seconds without output running [b'/srv/pokybuild/yocto-worker/a-full/yocto-autobuilder-helper/scripts/prepare-shared-repos', b'/srv/pokybuild/yocto-worker/a-full/layerinfo.json', b'/srv/autobuilder/repos/a-full-1785', b'-p', b'', b'-t', b'autobuilder.yoctoproject.org/valkyrie/a-full-1785'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=1308.781365
Comment 1 Mathieu Dubois-Briand 2025-06-12 13:03:22 UTC
a-full ubuntu2204-vk-1 mathieu/master-next completed at 2025-06-12 08:23:28+00:00
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1785/steps/4/logs/stdio
Comment 3 Tim Orling 2025-06-12 14:57:53 UTC
RP comments this means we are having trouble cloning quickly in the infrastructure. Sakoman also thinks he has seen this, which is stronger infrastructure hint.
Comment 5 Antonin Godard 2025-06-17 11:05:55 UTC
a-full ubuntu2004-vk-3 agodard/master-next completed at 2025-06-17 10:54:28+00:00
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1825/steps/4/logs/stdio
Comment 6 Antonin Godard 2025-06-20 12:16:34 UTC
a-full ubuntu2404-vk-1 agodard/master-next completed at 2025-06-20 08:45:52+00:00
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1847/steps/4/logs/stdio

Following builders were running at that moment:
buildperf-alma8
buildperf-debian11

a-full ubuntu2004-vk-1 agodard/master-next completed at 2025-06-20 09:08:48+00:00
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/1848/steps/4/logs/stdio

Following builders were running at that moment:
buildperf-alma8
buildperf-debian11
Comment 7 Randy MacLeod 2025-08-21 14:52:57 UTC
Another AI bot swarm issue that hasn't been seen since we put an Inubis (sp?) test in place.