cache/restore fails to hit if same paths given in different order #1426
Comments
KtorZ
added a commit
to KtorZ/cache
that referenced
this issue
Mar 7, 2025
Thanks to this comment which saved me some headache: actions#1491 (comment) related to actions#1561. related to actions#1491. related to actions#1426.
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As can be seen in this run, restore will hit or miss depending on the order of the paths given.
Not seen on that workflow, but if you use
actions/cache/save, it will complain that the cache already exists despite a restore having reported a missed cache, if both use different orders.Not a good practice on the user side to use different orders, but I guess that the actions could do some sorting to avoid this kind of pitfall.
The text was updated successfully, but these errors were encountered: