Hi @cyberpwnn ! Is the repo on which you are using cache public? If yes, can you share link to the workflow run. If not, can you share the logs here?

Hello,
I have the same error
logs

Seeing the same issue on this repo. Here's a representative action run:

Post job cleanup.
Post job cleanup.
/usr/bin/tar --posix --use-compress-program zstd -T0 -cf cache.tzst -P -C /home/runner/work/MetPy/MetPy --files-from manifest.txt
/usr/bin/tar: ../../../work/_temp/bdee9e41-e8-4f2a-9912-6eb32de36aa/cache.tzst: file changed as we read it
Warning: Tar failed with error: The process '/usr/bin/tar' failed with exit code 1
Post job cleanup.
Cache hit occurred on the primary key setup-python-Linux-pip-9225292fdf311547e1fda261cbc2734e26bc2c516bdcf7d87f5c7af6de21fb8c, not saving cache.

Can confirm this is still an issue.

zstd is installed but:

/bin/tar --posix --use-compress-program zstd -T0 -cf cache.tzst -P -C /home/ec2-user/actions-runner/_work/my-repo/my-repo --files-from manifest.txt
tar (child): zstd -T0: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now

@sammcj - your error seems to be a different one as the file/directory doesn't exist at the first place. Can you please check if the path(s) that you have provided in your configuration exist?

@MatthieuLeboeuf, @dopplershift @cyberpwnn can you please share the path (or list of folders) used for caching and approximate cache size after compression in your respective repos when you came across this issue?

So for my failure, I'm caching ~/local. It's the build products from the PROJ library to save me from building later, so maybe a few MB?

@dopplershift thanks for sharing the path. The logs you have shared are not available anymore. Requesting you to please share the run if you come across the situation again.

It's been failing pretty consistently for the last 6 months, so I appreciate you taking a look. Here's the most recent failure from last night.

@dopplershift I am planning to release a fix (v3.0.4) today, I'll let you know once its available for testing.

v3.0.4 is out and the same can be used to test this issue (no need to change anything in the workflow, actions/cache@v3 will point to the latest changes).

Do let us know if you come across the same problem again.

I am hoping the problem is resolved for all now. Hence closing the issue.

I can confirm that moving to @v3 fixes this particular issue for me.

I'm having a different problem now where it can't find the cache (after successfully saving), but the fact that you can't list what caches are present it making debugging more than a little difficult. I'll open an issue if I can ever get my hands around it.