Avoid uploading corrupted cache to S3 #74
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
chirgjn
force-pushed
the
fix-skip-upload-for-corrupted-cache
branch
from
66f611e
to
cfe55cd
Compare
|
Hi @chirgjn Thanks for the PR. It seems docker-compose is no longer available at latest version of GH Actions. I've fixed in 🤞 |
chirgjn
force-pushed
the
fix-skip-upload-for-corrupted-cache
branch
from
cfe55cd
to
2b77ac4
Compare
chirgjn
changed the title
|
Hi @gencer, Thanks for your response. I've rebased the PR, we can trigger a test run if the changes look fine to start testing. |
|
CI reports failures due to changes. |
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.
The generated tar file can be corrupted, which when used as cache will result
in failures. This PR adds a "check" and "retry" for tar file generation.