Skip to content
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

Fixed getCacheEntry failed: Cache service responded with 503 #2259

Closed
Limraj opened this issue Jun 13, 2022 · 3 comments
Closed

Fixed getCacheEntry failed: Cache service responded with 503 #2259

Limraj opened this issue Jun 13, 2022 · 3 comments
Labels
Milestone

Comments

@Limraj
Copy link
Collaborator

Limraj commented Jun 13, 2022

Description
There was a problem with the actions/cache@v2

There is a problem loading the war file to the cache using the actions/cache@v2 action:
Screenshot 2022-06-13 at 10 17 18

Which leads to the error:
Screenshot 2022-06-13 at 10 17 48

Links
bahmutov/npm-install#80
actions/cache#698
actions/cache#820

https://github.com/marketplace/actions/cache-anything-new
https://github.com/actions/cache
https://www.githubstatus.com/

@Limraj
Copy link
Collaborator Author

Limraj commented Jun 13, 2022

up version to v3 not work
Screenshot 2022-06-13 at 11 29 59

edit:
up version:
*actions/checkout from v2 to v3
*actions/setup-node from v1 to v3

same problem

Limraj added a commit that referenced this issue Jun 13, 2022
Limraj added a commit that referenced this issue Jun 13, 2022
…up version actions/setup-node from v1 to v3
@RWilliams-MicronAgritech

up version to v3 not work Screenshot 2022-06-13 at 11 29 59

edit: up version: *actions/checkout from v2 to v3 *actions/setup-node from v1 to v3

same problem

I use checkout v2, and my actions are now running.

steps: - uses: actions/checkout@v2 name: Use Node.js ${{ matrix.node-version }} - uses: actions/setup-node@v2 with: node-version: ${{ matrix.node-version }} # cache: 'npm'

Limraj added a commit that referenced this issue Jun 13, 2022
@Limraj
Copy link
Collaborator Author

Limraj commented Jun 13, 2022

We have the v2 version in use and there was this problem. In your case, the solution is the following comment line:
#cache: 'npm'
So you are not using the cache.

edit:
https://www.githubstatus.com/

Limraj added a commit that referenced this issue Jun 13, 2022
Limraj added a commit that referenced this issue Jun 22, 2022
…_failed_Cache_service_responded_with_503

#2259 Fixed getCacheEntry failed: Cache service responded with 503
@Limraj Limraj closed this as completed Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants