[v0.4] Don't fail fast CI workflow #444
Open
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
tomleb
force-pushed
the
fail-fast-ci-v0.4
branch
from
e867c48 to
33debd8
Compare
With flaky tests or Docker rate limit, it's very annoying to have a job's failure cancel another job. Instead, let all jobs run to completion, this way we can restart only the failed one.
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.
Issue: rancher/rancher#45231
Technically not required for rancher/rancher#45231 but related.
With flaky tests or Docker rate limit, it's very annoying to have a job's failure cancel another job. Instead, let all jobs run to completion, this way we can restart only the failed one.
Backport of #442