[libc++] Also restart failed CI jobs that die due to a Docker-in-Docker issue #118550
Conversation
This file contains hidden or 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
ldionne
changed the title
ldionne
force-pushed
the
review/fix-workflow-restart-libcxx
branch
3 times, most recently
from
b58f1b0 to
2ab66bd
Compare
ldionne
force-pushed
the
review/fix-workflow-restart-libcxx
branch
from
2ab66bd to
d265829
Compare
Member
Author
|
For some reason this PR is not helpful in reproducing the problem so I'll try other ways. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Since we moved to a Docker-in-Docker setup, CI jobs sometimes fail due to the Docker VM dying with 'context cancelled' errors. This is currently not recognized as a spurious failure, which leads to the job not being automatically restarted. This patch fixes that.