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

Infinite receiving #76

Open
Milo123459 opened this issue Sep 17, 2022 · 7 comments
Open

Infinite receiving #76

Milo123459 opened this issue Sep 17, 2022 · 7 comments

Comments

@Milo123459
Copy link

https://github.com/railwayapp/nixpacks/actions/runs/3073248385/jobs/4965261535#step:5:15564

Please let me know if you need more context.

@Swatinem
Copy link
Owner

Is this reproducible? I think this is rather an upstream problem. The whole cache code itself is just using upstream.

@Milo123459
Copy link
Author

Not sure, it just happened really.

@LesnyRumcajs
Copy link

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?

@ivankovnatsky
Copy link

We experiencing this quite often, I would say roughly 10% of all builds.

@Swatinem
Copy link
Owner

I’m pretty sure that is an upstream issue. This action delegates the whole caching step itself to the upstream @actions/cache package. Issues go here: https://github.com/actions/toolkit/issues

@ivankovnatsky
Copy link

Let's close this one then?

@abonander
Copy link

I don't see a relevant issue on actions/toolkit but this definitely still happens to us periodically, it's like the download bandwidth just slows to zero and stops, but it doesn't detect this and time out or try to recover: https://github.com/launchbadge/sqlx/actions/runs/6654941857/job/18355715032?pr=2545

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants