You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using the cache action, the path is used to generate a unique version.
Unfortunately depending on the runner type official or self-hosted) the workspace do changes and creates a different version.
This leads to a mistmatch and a failure.
To Reproduce
Steps to reproduce the behavior:
Have self-hosted AND github runners available
Create a workflow that cache some folders using ${{ github.workspace }}
Have multiple matrix start and restore the said cache
See failures on runs that are on a different type of runner than the one the cache was created on
Expected behavior
I do wonder why we actually care about the path at all when restoring?
If I did cache some folders, and I do want to restore them, shouldn't the cache key be enough to justify a proper cache match or miss?
Describe the bug
When using the cache action, the path is used to generate a unique version.
Unfortunately depending on the runner type official or self-hosted) the workspace do changes and creates a different version.
This leads to a mistmatch and a failure.
To Reproduce
Steps to reproduce the behavior:
${{ github.workspace }}
Expected behavior
I do wonder why we actually care about the path at all when restoring?
If I did cache some folders, and I do want to restore them, shouldn't the cache key be enough to justify a proper cache match or miss?
Might be related: #1377
The text was updated successfully, but these errors were encountered: