Post run error: "Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.!
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Post run, we are getting an error:
Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
Similar to these issues:
https://github.com/actions/setup-node/issues/801
https://github.com/actions/setup-node/issues/1137
Reading the output - everything seems fine, so this should be a warning instead of an error, since no cache is supposed to be saved. Can we force it to ignore this error?
Also, the directory specified does exist, so the error is also not correct.
Cache action as used:
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 reproducing the post-run error with the cache action configuration shown in the issue and inspect the cache action's output. Compare behavior when the configured path is absent versus present; done when the action reports the condition appropriately and handles an existing directory without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100