-
Notifications
You must be signed in to change notification settings - Fork 55
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
Labels
jira
For syncing to JIRA
Comments
I would probably just use a But... sigh ideally we do try to get to the bottom of the underlying issue. |
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 |
c4rt0
added a commit
to c4rt0/fedora-coreos-pipeline
that referenced
this issue
Feb 25, 2025
c4rt0
added a commit
to c4rt0/fedora-coreos-pipeline
that referenced
this issue
Feb 26, 2025
c4rt0
added a commit
to c4rt0/fedora-coreos-pipeline
that referenced
this issue
Feb 26, 2025
We had an issue recently where kola-aws and kola-gcp were killed in the fetch metadata step because they started at the same time. This fix locks the buildfetch stage which only takes a few seconds. fixes: coreos#1079
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 120sThe text was updated successfully, but these errors were encountered: