actions / actions/cache

windows-latest cache is not compatible with windows-11-arm

Open
#1,622 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
5.6k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

Using actions/cache/save@v4 in jobs under windows-11-arm, even when using enableCrossOsArchive: true, results in "Cache not found for input keys" when trying to restore the cache key in other OS using actions/cache/restore@v4, and vice-versa.

This minimal project's pull request illustrates the problem: https://github.com/pedrolcl/cachetest/actions/runs/15818554368/job/44582204888?pr=1
The result is that two caches are produced with the same key: https://github.com/pedrolcl/cachetest/actions/caches?query=key%3Asoundfont.dls

Image

The problem seems to be that in the windows-11-arm image zstd is omitted, so the gzip method is used instead. Every other image, like Windows-2022, has zstd and it is the preferred method. Funny thing is that the gzip cache version is smaller than the zstd one in this case.

Is there any known workaround for this? If not, maybe we could request another input for "preferred compression method"?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the cache workflow using actions/cache/save@v4 and actions/cache/restore@v4 across windows-11-arm and another Windows image, using the linked minimal project and run. Compare the zstd and gzip paths and cache keys. Done means identifying a supported workaround or defining the required change so caches can be restored across these runners.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.