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
[Test/build] 💬 ::debug::Archive Path: /tmp/5f9fa2f4-9113-428e-866b-27aadd5fc7e0/cache.tzst
| [command]/usr/bin/tar --posix -cf cache.tzst --exclude cache.tzst -P -C /tmp/my home --files-from manifest.txt --use-compress-program zstdmt
| /usr/bin/tar: /tmp/my: Cannot open: No such file or directory
| /usr/bin/tar: Error is not recoverable: exiting now
[Test/build] 🚧 ::warning::Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
[Test/build] ✅ Success - Post actions/cache@v4
The solution should be to enclose the argument to tar with quotes -C '/tmp/my home'
[Test/build] 💬 ::debug::Archive Path: /tmp/9ab78ede-b291-426c-9134-83a98efed61d/cache.tzst
| [command]/usr/bin/tar --posix -cf cache.tzst --exclude cache.tzst -P -C /tmp/my home --files-from manifest.txt --use-compress-program zstdmt
| /usr/bin/tar: /tmp/my: Cannot open: No such file or directory
| /usr/bin/tar: Error is not recoverable: exiting now
[Test/build] 🚧 ::warning::Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
[Test/build] ✅ Success - Post actions/cache@v4
Additional information
No response
The text was updated successfully, but these errors were encountered:
Act could stop mirroring the spaces of your host OS into the container (docker backend) to avoid common problems / you would work in a folder outside your user profile
Bug report info
Command used with act
Describe issue
When running
actions/cache
in a build, it fails if current folder contains a space.This is the full command sequence you can use for reproducing it:
The error in console is:
The solution should be to enclose the argument to tar with quotes
-C '/tmp/my home'
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: