Caching fails due to use of legacy action/cache

[JanCBrammer]

Caching fails with

Warning: Failed to restore: Cache service responded with 422
Warning: No cached files found at path "/home/runner/work/foo/emsdk-cache" - downloading and caching emsdk.
[...]
Failed to save: Unable to reserve cache with key Deploy GitHub Pages-4.0.6-linux-x64, another job may be creating this cache.
More details: This legacy service is shutting down, effective April 15, 2025. Migrate to the new service ASAP. For more information: https://gh.io/gha-cache-sunset

Most likely due to sunsetting of actions/cache, see https://github.com/actions/toolkit/blob/main/packages/cache/README.md#%EF%B8%8F-important-changes.

[agriyakhetarpal]

We've also been hitting this recently. From the README note you linked, it looks like not much is needed beyond updating to use v4 of actions/cache:

Upgrading to the recommended version should not break or require any changes to your workflows beyond updating your package.json to version 4.0.0.

[agriyakhetarpal]

I've opened a PR to fix this above, and it should work! :)

[agriyakhetarpal]

To those subscribed here: in the meantime, I created a friendly fork at https://github.com/pyodide/setup-emsdk/ and a corresponding release at https://github.com/pyodide/setup-emsdk/releases/tag/v15 for our use, which directs to this repository for accreditation. It will be archived once #48 is merged and included in a release.

It can be used by swapping out the actions from

- uses: mymindstorm/setup-emsdk@v14

to

- uses: pyodide/setup-emsdk@v15

[Naros]

Is there a way to have setup-emsdk install into a fixed directory so that it can work in cooperation with ccache. Right now, ccache launches Emscripten, but due to the emsdk action installation using a random _temp path, this breaks cache hits.

[agriyakhetarpal]

Is there a way to have setup-emsdk install into a fixed directory so that it can work in cooperation with ccache. Right now, ccache launches Emscripten, but due to the emsdk action installation using a random _temp path, this breaks cache hits.

@Naros, I believe that is what the actions-cache-folder: input does, right?

[Naros]

Hi @agriyakhetarpal, I tried that.

So my issue here is that when using ccache + setup-emsdk, no matter the combinations, ccache always reports 100% cache misses, which causes my Emscripten builds to take 20+ minutes.

So instead of using hendrikmuhs/ccache-action@v1.2.17 which works for all my non-Emscripten builds, I opted to try and use mozilla-actions/sccache-action@v0.0.9 and that seemed to work as expected, but I genuinely would prefer to use the former rather than the latter.

I tried all sorts of things, and my only conclusion is that despite my efforts, the fact Emscripten instealls into _temp/<hash> directory which is different on each execution, ccache is less relaxed about this and forces cache misses.

[agriyakhetarpal]

Hi @agriyakhetarpal, I tried that.

So my issue here is that when using ccache + setup-emsdk, no matter the combinations, ccache always reports 100% cache misses, which causes my Emscripten builds to take 20+ minutes.

So instead of using hendrikmuhs/ccache-action@v1.2.17 which works for all my non-Emscripten builds, I opted to try and use mozilla-actions/sccache-action@v0.0.9 and that seemed to work as expected, but I genuinely would prefer to use the former rather than the latter.

I tried all sorts of things, and my only conclusion is that despite my efforts, the fact Emscripten instealls into _temp/<hash> directory which is different on each execution, ccache is less relaxed about this and forces cache misses.

Thanks for reporting the problem, @Naros. I'll try to find some time in the near term to take a closer look at this. Do you have some logs I can look at? It would also be helpful to see the difference between the two ccache actions to gauge why one works with Emscripten and the other one doesn't.