-
Notifications
You must be signed in to change notification settings - Fork 70
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
Error: getCacheEntry failed: Cache service responded with 503 #80
Comments
I'm getting a similar error but with 403: Run bahmutov/npm-install@v1
running npm-install GitHub Action
trying to restore cached NPM modules
Error: Cache service responded with 403
at Object.<anonymous> (/home/runner/work/_actions/bahmutov/npm-install/v1/dist/index.js:3503:19)
at Generator.next (<anonymous>)
at fulfilled (/home/runner/work/_actions/bahmutov/npm-install/v1/dist/index.js:3427:58)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
Error: Cache service responded with 403 |
I have the same error as @bitttttten when trying to run my action on a pull_request |
I'm getting the 403 error on
If it makes any difference, I'm checking out the HEAD branch of the pull_request:
|
I am hitting the same issue today on one of the jobs, but not |
I'm doing transition to Github Actions and this error
shows up more than often. I feel that in case of reading the cache it should fallback with installing the dependency, not fail the build, right? |
I'm getting this error when the event is |
@anshulsahni I'm hitting the same thing as you in a |
Just got this error now: |
Can there be a failover so that if the Cache fails to be retrieved, the standard npm install command gets executed instead. This will be able to still run the job if github actions have issues with caches. |
Me too, but with
14.x works great: UPD: See a workaround below: #80 (comment) |
Yeah all my actions are failing now, too... |
Same here What's going on? We have production build failed, which is critical |
[For NodeJS] So, I had an investigation. It doesn't work if cache was enabled. Try to disable cache by commenting Warning: It'll slowdown your action. It is just temporary solution!!! jobs:
check-format:
runs-on: self-hosted
steps:
- uses: actions/checkout@v2
- name: Use Node.js 16.x
uses: actions/setup-node@v2
with:
node-version: 16.x
# cache: 'npm' <--- Action works only if cache disabled.
- run: npm i
- name: Check format
run: npm run check-format
- name: Linting
run: npm run lint |
It wasn't working for me 5min ago (503 error), I retried now and it's working |
same here, looks like a github failure ... |
This worked for me, thanks @afrokick |
I was also facing the same issue , I checked the github repo for the and now its working 👍🏻 .. May be you guys also try this method . And also its good practice to keep upgrading the version of the github action step |
Just tried, doesn't work for v3. Only works with disabled cache. |
Yep, facing issue with ....
- name: Setup node env 📦
uses: actions/setup-node@v3
with:
node-version: ${{ matrix.node }}
check-latest: true
- cache: 'npm'
.... |
We're facing the same issue.
No cache key is specified. |
Same issue here
|
how is it related to |
@lossless1 it's probably invalidating the cache |
Getting the same error here for actions/setup-node@v2 |
Getting this issue from past 10 mins now. |
Getting the same error here for
|
Npm caching is currently failing. See: bahmutov/npm-install#80
Updating to Checkout v. 3 didn't help. Didn't try updating setup-node to v. 3, but disabling npm cache did the trick. |
How do I disable cache |
Disable the cache. It should work |
Read above. |
Thank you |
I have |
No need to upgrade anything. |
still failing for me. |
Disabling the cache:npm works for me. |
are you all turning the cache on again and it works after? as I don't really want to just "turn off the cache" ideally 🙈 |
Yes disabling (commenting out) the cache works. It's not about the setup-* version. Re-running failed jobs may work (tested) but it's not reliable. If you HAVE to release today, just remove the cache but they will get it to work eventually I guess. The thing here is, we need a way to disable cache without commiting t master branch imho Is this happening because of the underlying actions/cache action? If so we need to know, we use actions/cache to cache angular build files too. |
Ruby budnle-cache is failing too! :( |
After turning the cache on again, it failed. It is a temp solution. |
It is a service issue. |
No production releases today, boys 😃 |
Oh my god... We have to do hotfix...our team is still wating |
Hi, I am having the same issue in my CI system just started occurring today for the first time. It was working fine without any issue until Friday. Run actions/setup-node@v2 Is it an issue from github side and will it be solved soon? We can live without cache until then if that is the case? |
Yes, just disable cache for some time while Github fixing this issue |
updating from v2 to v3 solved my problem
|
It's up again, boys, the dream is alive |
The issue should be solved, it seemed a problem in the github actions side. You can check here for the status: https://www.githubstatus.com/ |
Can you please add the ability to disable the cache without commiting to master ? |
I have seen this error pop up several times in the past few days
The error seems to originate from this code, which does not seem to be part of this repository
I've set
ACTIONS_STEP_DEBUG
totrue
for future runs and will let you know if that yields any helpful information.The source code above suggests that
maxAttempts
might be configurable? Is there an option I can set to retry requests in case of a 503?The text was updated successfully, but these errors were encountered: