-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Properly check for cache hits. #2172
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am surprised this change is needed, it was working as is at some point.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Vincent: Searching for "cache-hit" in https://github.com/actions/cache, I found that we are testing cache-hit
in the same way as the sample code.
Are you sure this pull request is necessary?
Let's put this one on the back burner, maybe I thgought it was necessary because of a cache miss. |
cache-hit is a boolean.
This reverts commit 624e365.
The cache hit was not checked properly: the answer from the action has to be sent back to the main workflow. This bug was just introduced in #2174 |
steps.cache-ext.outputs.cache-hit != 'true'
is actually always true becausesteps.cache-ext.outputs.cache-hit
does not exist anymore, as the stepcache-hit
is now hidden in the cache action. Thecache-hit
information has to be sent back from the cache action.