cache restore on versions 3 and 4 not working

[mark-jordanovic-lewis]

The functionality of the cache action seems to be completely broken.

Configurations attempted:

• save/restore actions @v4
• save/restore actions @V3
• base cache action @v4
• base cache action @V3

Experimental Workflow and Results

The cache is being accessed on the same branch, in the same workflow (and later, if the first set of jobs pass).

These screenshots pertain to the run of base cache action @V3, they are consistent across all configurations.

Cache version 2 works as expected.

Would definitely prefer to use the most recent versions.

[mark-jordanovic-lewis]

Cause of the above issue is a difference in the actions/checkout version. There must be a difference in the way they reference the branch.

[matthiasPOE]

Im currently getting:

Failed to save: Unable to reserve cache with key db09ccc890352b660ddd94bbcf7ce4b880b254099c5050c6059b00b0b4c5777e, another job may be creating this cache. More details: Cache already exists.

Not sure if its related but even deleting all caches it wont recreate them...

[serpro69]

Same issue here. Have been wracking my brain why this doesn't work and then wanted to eventually open an issue and found out there's one already.
Trying v2 now as recommended above.

upd: v2 works as expected

[yrtimiD]

@mark-jordanovic-lewis just to ensure, do you have exactly same value in the "path" parameter both in save and restore? I had different and restore failed too.

[mark-jordanovic-lewis]

Correct. Same parameters in each use of the action.

[SimonSchick]

We are seeing similar issues on v4 where the cache is not found despite clearly existing, only 1/5 runs are picked up correctly, is the cache action not reliable-ish?

[njzjz]

I encountered the same issue. Save v4 + restore v2 cannot work as well. Using save v2 + restore v2 can resolve the problem. However, it seems that Node.js 16 is going to be deprecated.

[njzjz]

I encountered the same issue. Save v4 + restore v2 cannot work as well. Using save v2 + restore v2 can resolve the problem. However, it seems that Node.js 16 is going to be deprecated.

I just found the reason: in v4, the path for restore and save must be the same. The error message doesn't give such information.

[wmertens]

@njzjz I'm encountering this problem too and the paths are the same for me