ensure single retry of all buildkite jobs exiting w/ code 1 (common error) #6355
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
O1ahmad
added
the
ci-build-me
lk86
approved these changes
Oct 13, 2020
|
Deploy preview for mina-staging ready! Built with commit 2be1ee2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to Buildkite's agent exit code documentation, job exit status of
1is the most common error (which is also observably supported by "flakey" jobs throughout Coda's pipeline which generally fail with exit-code 1 and are resolved by a single retry.)This change adds a single automatic retry for all jobs failing in this way as a first defense against flakey errors.
Testing: Buildkite linting + CI
Checklist: