Fix cache restoration for Hypothesis CI job#121756
Merged
Uh oh!
There was an error while loading. Please reload this page.
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.
Previously, the CI workflow job running Hypothesis was mistakenly set up to use a cache restoration key prefixed with a leading hyphen [1]. This was done in an attempt to figure out the right format for the
actions/cacheinput argument calledrestore-keysas the official examples tend to be confusing [2].This results no cache being found for the Hypothesis database on lookup [3] and the logs contain the following:
The patch corrects that by dropping the unintended characters from the catch-all cache key.