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

Try to ensure that Codecov always uploads a coverage report. #7656

Closed
seanlip opened this issue Sep 21, 2019 · 1 comment
Closed

Try to ensure that Codecov always uploads a coverage report. #7656

seanlip opened this issue Sep 21, 2019 · 1 comment
Assignees

Comments

@seanlip
Copy link
Member

seanlip commented Sep 21, 2019

Sometimes, Codecov fails to upload a coverage report. See e.g. #7621 (comment) -- Codecov did not block that PR as it couldn't upload the coverage report, causing the main codebase to have backend coverage failures.

The complete log at that time was:

Error: HTTPSConnectionPool(host='codecov.io', port=443): Max retries exceeded with url: /codecov/v4/raw/2019-09-17/6BBD04BAB28362906B7CAACFE0DF5AE7/0c88cf559bcb7f15a297dd3b26421857282fb475/15ca3dc1-2d7f-4cbd-be21-b934f7a34b39.txt?AWSAccessKeyId=AKIAIHLZSCQCS4WIHD4A&Expires=1568726448&Signature=ySd0BtSHoOpnjrvogq0fenmKChw%3D (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7ff4709c9890>: Failed to establish a new connection: [Errno 110] Connection timed out',))

The solution to this seems to be retrying till the coverage is uploaded successfully. Here is the context: link. The aim of this issue is to try this out in a PR.

@seanlip
Copy link
Member Author

seanlip commented Nov 5, 2019

I think we've given up on Codecov (and are using CodeClimate instead for the primary check), so I'm closing this issue.

@seanlip seanlip closed this as completed Nov 5, 2019
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

2 participants