v3.0.6 introduced dependency on zstdmt (not just zstd) for cache creation, fails on Windows

[rfay]

As of v3.0.6 this apparently requires zstdmt, not just zstd, which is a major departure. I have not found any Windows binaries for zstdmt. I'm not sure it's available elsewhere either.

This is what happens:

##[debug]Archive Path: C:\drud-actions-runner\_work\_temp\ff5371eb-5f15-4474-8084-5df62fc397fa\cache.tzst "C:\Program Files\Git\usr\bin\tar.exe" --posix --use-compress-program zstdmt -cf cache.tzst --exclude cache.tzst -P -C C:/drud-actions-runner/_work/ddev/ddev --files-from manifest.txt --force-local /bin/sh: zstdmt: command not found /usr/bin/tar: cache.tzst: Cannot write: Broken pipe

It was already hard enough to get zstd onto Windows... It's sad to break things now by changing the tar compression format even father.

Previous instructions for getting zstd into a Windows machine were at #580 (comment)

[kotewar]

Hi @rfay
Thanks for reporting this. We are aware of the issue with Windows machine and the work is already in progress for the same.

The issue being tracked here.

[lvpx]

Hi @rfay, the tar compression(zstd) on Windows while using the above workaround should now work. Please test and let us know if the issue is now resolved.

[kleisauke]

I can confirm that v3.0.8 fixes the issue, see e.g. commit kleisauke/wasm-vips@50c7d00.

[lvpx]

Closing the issue since a fix has been deployed and tested. Feel free to re-open if recurs.

[rfay]

@pdotl I assume we still have to do the bizarre installation of zstd on windows self-hosted runners still, true? Did that make it into docs?

[lvpx]

@rfay we are adding the above workaround to the docs and will also document installation of zstd for windows self-hosted runners. If you are only using Windows self-hosted runners and not doing any cross-os caching as above, zstd is not required. The action will fallback to using gzip if it does not find zstd installed.

[rfay]

Yeah, I do cross-OS caching.