-
Notifications
You must be signed in to change notification settings - Fork 1.3k
codecov.io is flaky and can fail builds #15095
Comments
@friedbunny I've never seen this before, so thanks for ticketing.
Can you link to a few builds where this happened? Do you see any pattern? Given I've not seen this in other repos (and we have a lot with codecov enabled), perhaps gl-native is hitting this more often due to the size of the upload? How big is it?
Doubt this would help. The download of that file is tiny and the failure is in the put of coverage data. But definitely fine to check the code in if you want. |
Thanks, @springmeyer — you’re definitely right about checking in the script not making a difference; I misread the (very short 😅) log and was thinking it was the script download timing out, not the upload.
I don’t see a pattern, since this is failing on iOS-only changes (which aren’t included in the coverage). As for the size of the upload, that’s something that’ll need investigation. |
Another example: https://circleci.com/gh/mapbox/mapbox-gl-native/307070 |
It appears that this is a common issue with codecov.io — codecov/codecov-python#158 (comment). Workarounds look like just retrying it until it succeeds. For now, I’ve opted to not let it fail builds: #15248 |
This issue has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
When codecov.io connectivity is poor (which seems to happen with some frequency), some of our (otherwise completely successful) builds fail with:
I’m not sure it would mitigate the issue, but it seems inherently unsafe to be downloading and executing an arbitrary bash script for every run — committing the script to our repo would at least eliminate one network request.
/cc @jmkiley @springmeyer
The text was updated successfully, but these errors were encountered: