Error: getCacheEntry failed: Cache service responded with 503
See original GitHub issue2022-06-13T06:46:29.7622187Z ##[group]Run actions/setup-node@v2
2022-06-13T06:46:29.7622425Z with:
2022-06-13T06:46:29.7622601Z node-version: 16.13
2022-06-13T06:46:29.7622858Z cache: npm
2022-06-13T06:46:29.7623136Z cache-dependency-path: ./slack-adapter/package-lock.json
2022-06-13T06:46:29.7623405Z always-auth: false
2022-06-13T06:46:29.7623606Z check-latest: false
2022-06-13T06:46:29.7623978Z token: ***
2022-06-13T06:46:29.7624149Z ##[endgroup]
2022-06-13T06:46:29.9263615Z Attempting to download 16.13...
2022-06-13T06:46:30.1968736Z Acquiring 16.13.2 - x64 from https://github.com/actions/node-versions/releases/download/16.13.2-1681281899/node-16.13.2-linux-x64.tar.gz
2022-06-13T06:46:30.5470929Z Extracting ...
2022-06-13T06:46:30.5583930Z [command]/usr/bin/tar xz --strip 1 --warning=no-unknown-keyword -C /home/runner/work/_temp/1c9fdfcb-b4e4-45cc-b8c0-879d4d188913 -f /home/runner/work/_temp/288baaa0-6ffa-45e6-b176-3504aa37feb4
2022-06-13T06:46:31.3994436Z Adding to the cache ...
2022-06-13T06:46:32.2973296Z Done
2022-06-13T06:46:32.2987622Z [command]/opt/hostedtoolcache/node/16.13.2/x64/bin/npm config get cache
2022-06-13T06:46:32.5559356Z /home/runner/.npm
2022-06-13T06:46:42.7419366Z ##[error]getCacheEntry failed: Cache service responded with 503
Description: setup-node fails with cacheing error
Action version: @actions/setup-nodev2
Platform:
- Ubuntu
- macOS
- Windows
Runner type:
- Hosted
- Self-hosted
Tools version:
node: 16.13.2
Repro steps:
Workflow file:
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
with:
node-version: 16.13
cache: "npm"
cache-dependency-path: ./slack-adapter/package-lock.json
Expected behavior: Success
Actual behavior: Failing on cache service
Issue Analytics
- State:
- Created a year ago
- Reactions:117
- Comments:21 (1 by maintainers)
Top Results From Across the Web
getCacheEntry failed: Cache service responded with 503 ...
I have seen this error pop up several times in the past few days The error seems to originate from this code, which...
Read more >getCacheEntry failed: Cache service responded with 503
I too faced the same problem. It is because of the cache server not responding that includes internal server error or any other....
Read more >Common 503 errors on Fastly | Fastly Help Guides
Error 503 backend fetch failed. This error occurs when the connection closes before Fastly cache servers are done reading the response. This ...
Read more >getCacheEntry failed: Cache service responded with 503
Answer a question I am trying to check the lint on the gitubaction. my github action steps are as below lint: name: Lint...
Read more >なかざん on Twitter: "GitHub Actionsのsetup-nodeで ...
GitHub Actionsのsetup-nodeで、cacheオプションを指定すると死ぬバグが起きて ... Error: getCacheEntry failed: Cache service responded with 503 ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, all 👋 ! We are working on that issue. Sorry for the inconvenience.
actions/cache
issue aside, maybe the this action should allowrestoreCache()
to fail and continue regardless as if there was no cache.