Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a startup delay to kola-aws and kola-gcp jobs #1079

Open
jbtrystram opened this issue Jan 7, 2025 · 2 comments
Open

Add a startup delay to kola-aws and kola-gcp jobs #1079

jbtrystram opened this issue Jan 7, 2025 · 2 comments
Assignees
Labels
jira For syncing to JIRA

Comments

@jbtrystram
Copy link
Contributor

We had an issue recently where kola-aws and kola-gcp where killed in the fetch metadata step because they started at the same time.

Add a parametrized delay and have the build job pass a random delay between 0 and 120s

@jbtrystram jbtrystram added the jira For syncing to JIRA label Jan 7, 2025
@jbtrystram jbtrystram self-assigned this Jan 7, 2025
@jlebon
Copy link
Member

jlebon commented Jan 22, 2025

I would probably just use a lock for this instead of a random delay.

But... sigh ideally we do try to get to the bottom of the underlying issue.

@dustymabe
Copy link
Member

dustymabe commented Jan 23, 2025

I would probably just use a lock for this instead of a random delay.

good idea. that works too. The buildfetch doesn't take long so it shouldn't be too disruptive to do this across all jobs that buildfetch at the beginning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira For syncing to JIRA
Projects
None yet
Development

No branches or pull requests

3 participants