Cache action fails to match successfully uploaded key
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
First build
During the first build there was no match, so everything was built from scratch and at the end the job, the cache was successfully uploaded with the expected key:
https://github.com/infogulch/scryer-prolog/actions/runs/5352326258/jobs/9707117537
Second build
In a subsequent build one hour later, the key matched exactly, it still did not find a match and rebuilt from scratch again:
https://github.com/infogulch/scryer-prolog/actions/runs/5352743821/jobs/9707964066
Why did it not restore from the cache? It's clearly present: https://github.com/infogulch/scryer-prolog/actions/caches
ubuntu-20.04_rustc-2023053190c5_cargo-85a461c9dd680796bb3bea6e727ef52f589ac820d7d491c10aec6516477bb45c
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the first and second linked GitHub Actions job runs with the cache listing and the reported key. Trace why the exact uploaded key was not restored, then confirm the explanation against the observed cache behavior. Done means the cause is identified and a focused fix or documented resolution is validated against a subsequent cache run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100