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

Error: getCacheEntry failed: Cache service responded with 500 in new workflow #378

Closed
4 of 5 tasks
dominikg opened this issue Dec 11, 2021 · 7 comments
Closed
4 of 5 tasks
Labels
bug Something isn't working

Comments

@dominikg
Copy link

Description:
setup-node fails with an error

Run actions/setup-node@v2
  with:
    node-version: 16
    cache: pnpm
    cache-dependency-path: **/pnpm-lock.yaml
    always-auth: false
    check-latest: false
    token: ***
Found in cache @ /opt/hostedtoolcache/node/16.13.0/x64
/opt/hostedtoolcache/node/16.13.0/x64/bin/pnpm store path
/home/runner/.pnpm-store/v3
Error: getCacheEntry failed: Cache service responded with 500

Action version:
setup-node@v2

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:
node 14 + 16
pnpm 6.23

Repro steps:
Workflow here https://github.com/svitejs/vite-plugin-env-config/blob/main/.github/workflows/ci.yml

It uses setup-node twice:

Expected behavior:

setup succeeds

Actual behavior:
setup fails
log shows a 500 error for cache service
https://github.com/svitejs/vite-plugin-env-config/runs/4494014103?check_suite_focus=true#step:5:12

Additional information

  • The repo is very new and cloned from a template. other repos with a similar setup don't show this behavior
  • These are the initial workflow runs, there hasn't been a success. Maybe some initializaion failed?
@dominikg dominikg added bug Something isn't working needs triage labels Dec 11, 2021
@dominikg
Copy link
Author

seems to be related to actions/cache#698

@egonbraun
Copy link

Had a similar issue yesterday with the setup-python action, tried again today and it is working fine. It seems like it was a temporary issue. I check GitHub status page and couldn't find any incident related to that though. The only one I found was this: https://www.githubstatus.com/incidents/tc051c121cs7

But it is not related.

@dominikg
Copy link
Author

workaround is to simply disable cache parameters by commenting them. Will download more dependencies but no more errors)

@dominikg
Copy link
Author

dominikg commented Dec 13, 2021

upstream issue discussion hints that this may be fixed now

actions/cache#698 (comment)

still setup-node may want to think about how to handle caching related errors.

@PaulRBerg
Copy link

Can confirm that it's fixed now.

@dmitry-shibanov
Copy link
Contributor

Hello everyone. Thank you for your report. I'm going to close the issue, because the initial one was resolved. If you have any concerns feel free to ping us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants
@dominikg @egonbraun @PaulRBerg @gregnrobinson @dmitry-shibanov and others