Cache miss even though has cache before with exact restore key
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
I have already run cache action on base branch before, it saved with restore key macOS-ruby-<my Gemfile.lock has>. But after 4 day not using that cache, today I run an action and when to the step cache, it say cache not found for inputs key: the key with the exact key that saved before.
I'm using cache v3.
Is this an expected behavior of cache action, how can I expand the timeout of cache file. I don't want after some days off, I have to bundle install again.
Thank you
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
The report does not name a source file, test, workflow file, or complete cache logs. Start by reproducing the cache-v3 workflow with the exact restore key described in the issue, then inspect cache retention and lookup behavior; done means explaining why the previously saved cache is unavailable and documenting the supported retention behavior.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100