-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Warning: Cache not found" on first run in branch #1552
Comments
Example workflowhttps://github.com/cypress-io/github-action/actions/workflows/example-install-only.yml Renovate creates a new branch
|
Debug logs
|
I'm trying to reproduce this in a simpler example and I'm not getting the warning, so I guess there is something subtle going on. I'll keep looking. |
This is something we plan to fix - a cache miss is expected behavior and should not be a warning. |
I am relieved to hear that! I was scratching my head a little as I was having difficulty reproducing it in all situations. |
@MikeMcC399 thanks for posting this bug. I started working on a new workflow using actions/cache and never saw this behavior previously and thought I was going crazy |
I saw that there is a new release actions/cache@4.2.1 Will the v4 is currently 1bd1e32 Edit: I see this is queued up in https://github.com/actions/cache/actions/runs/13396823681 so no need to answer! |
@MikeMcC399 the major tags (v4 and v3) should now be updated to fix this behavior, thanks again for reporting! |
Thanks very much for fixing and letting me know! 👍🏻 I ran through my repro steps and there is no more warning. First run
Second run
Closing as resolved! |
Current behavior
'actions/cache@v4' (SHA:1bd1e32a3bdc45362d1e726936510720a7c30a57)
actions/cache@v4.2.0
displays a warning such as:
when a GitHub Actions workflow contains:
and the workflow is running for the first time in a branch.
This is a regression compared to how it used to work.
Expected behavior
No warning should be issued when a workflow runs for the first time in a branch.
Caches are linked to branches and if a workflow runs for the first time in a branch, then it is an expected condition that there is no cache available.
Warnings should only be issued if some corrective action is necessary. In this situation no user corrective action is necessary. After the workflow has run once, a cache will be established and any subsequent runs will use the cache. The situation is self-correcting.
The text was updated successfully, but these errors were encountered: