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
Infinite receiving #76
Comments
Is this reproducible? I think this is rather an upstream problem. The whole cache code itself is just using upstream. |
Not sure, it just happened really. |
Hey @Swatinem, seems we encountered a similar issue https://github.com/ChainSafe/forest/actions/runs/3246430665/jobs/5325159334 Do you have any pointers except for timing out early? |
We experiencing this quite often, I would say roughly 10% of all builds. |
I’m pretty sure that is an upstream issue. This action delegates the whole caching step itself to the upstream |
Let's close this one then? |
I don't see a relevant issue on |
https://github.com/railwayapp/nixpacks/actions/runs/3073248385/jobs/4965261535#step:5:15564
Please let me know if you need more context.
The text was updated successfully, but these errors were encountered: