Restore action doesn't actually fail workflow even when fail-on-cache-miss is true
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
- If you have found a security issue please submit it here
- If you have questions about writing workflows or action files, then please visit the GitHub Community Forum's Actions Board
- If you are having an issue or question about GitHub Actions then please contact customer support
If your issue is relevant to this repository, please delete this text and continue to create this issue. Thank you in advance.
I'm using v4.0.0 of the Restore action, and I've noticed consistently that if there's a cache miss, that the step of the workflow errors, but it does not fail the job/workflow
I get this all the time
Error: Failed to restore cache entry. Exiting as fail-on-cache-miss is set.
But then the job proceeds just fine and after it's done I see a checkmark in the "workflow summary" page for that job.
I would expect that it should fail the job right at that step as soon as the cache miss occurs
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
Reproduce the cache miss with the v4.0.0 Restore action and fail-on-cache-miss enabled in a GitHub Actions workflow. Inspect the Restore action's error handling and verify that a cache miss causes the workflow job to fail at that step, rather than continuing to a successful checkmark.
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
- Mostly clear
- Newbie friendliness
- 38/100