Add check action
#1095
Closed
Add check action
#1095
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
Contributor
|
@cdce8p, I'll review this shortly and also discuss with my team regarding this PR and your comment on the other one. This might take some time, but thanks for your contribution again! 😃 |
Contributor
Author
Contributor
|
Sorry for the delay, I'll review the PR today. @cdce8p |
Contributor
Author
Awesome, thanks! Just updated all PRs to include the zstd fix. |
Contributor
Author
|
Now that #1041 has been merged, I'm going to close this one. Please feel free to reuse any of it in case something like this should be added in the future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Alternative or in addition to #1041 as suggested by @kotewar in #1041 (comment).
Add a dedicated action to check if a cache entry exists without actually downloading it.
Motivation and Context
Fixes #901
Fixes #831
#1020 (comment)
#1020 (comment)
If dependency install / cache setup and the actual tests are split across multiple jobs, it's often unnecessary to restore the cache if an exact cache-hit occurred. Similarly, if the cache is created from scratch, it's only necessary to know if a cache entry already exists.
Using
dry-runin these cases saves time and resources, especially for larger caches which don't need to be restored.How Has This Been Tested?
Added test case and run a test workflow using the feature branch.
Screenshots (if appropriate):
--
Types of changes
Checklist: