-
Notifications
You must be signed in to change notification settings - Fork 207
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
Exception: Request failed after too many retries #1547
Comments
I'm getting this starting today as well (repeatedly). Seems to only be affecting Linux and Windows runners in my case. macOS is okay (for now). https://github.com/LizardByte/Sunshine/actions/runs/10427264605 |
Hi there, we would like to chime in and report that we are being tripped by the same problem, starting to be observable since about an hour ago on two of our public repositories commons-codec and cratedb-toolkit, see 12. We guess the response is just right with Please advise if you think the problem might be on our end in any way. With kind regards, Footnotes |
+1 |
Facing the same issue. The script has been unchanged, running fine for a long time. I don't believe it's my/our problem. |
I think this may have been a result of https://status.codecov.com/incidents/1g1pznmcxr8t |
Hi there,
I've been using Codecov for many open-source and private repos because of it's feature-rich functionality. Thank you for providing this product to the open-source community!
After the switch to v4, the reporting is being extremely unstable with PRs randomly failing for different types of projects (there has been many issues reported and multiple PRs trying to fix this).
With this config:
My latest problem appear today out of nowhere:
In my branch, where the setup is trivial, token was rotated, version was pinned to the latest available, the config of GHA is exactly as per README.md, yet the action cannot complete successfully.
The error
Exception: Request failed after too many retries
is kinda useless - it does not explain the reason.Question to developers
Can this issue please be used to consider extending the logging to provide extended information on the cause of failures?
Can we also know in the log if the cause is a Codecov own service unavailability? It is understandable if the service is down (every service requires a maintenance once in a while), we just want to know in logs that it is on Codecov's side. Also, https://status.codecov.com/ shows that everything is operational, while in fact, it is not.
Question to managers and product owners ion Codecov
I apologize for the bluntness, but it’s challenging to recommend your product to my clients when these unresolved issues have persisted since the release of version 4 six months ago. The frequent PR failures are hindering our development teams so much that they are considering moving away from Codecov.
I'm hoping that the stability of this GHA can be prioritised.
The text was updated successfully, but these errors were encountered: