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

Coverage not uploading to Codecov #760

Closed
gtdang opened this issue May 7, 2024 · 0 comments · Fixed by #761
Closed

Coverage not uploading to Codecov #760

gtdang opened this issue May 7, 2024 · 0 comments · Fixed by #761
Assignees

Comments

@gtdang
Copy link
Collaborator

gtdang commented May 7, 2024

Unittest actions have been failing since switching to using the codecov-action v4 in #758 .

Codecov uploads have sporadically been failing due to rate-limiting of 'tokenless' uploads. It is not actually tokenless, see explanation below.

If Codecov detects that reports are being uploaded from a fork of an open source repository, Codecov will automatically switch to tokenless uploading...Token-less uploads still use a token to upload to Codecov - just that it's Codecov's Github token instead of the project's own. As such, uploading to Codecov via tokenless (whether it's via forks, or by an older version of the Codecov action) ends up consuming from the shared request pool of a lot of Codecov users, instead of your own. Therefore, there may be cases when uploading to Codecov via tokenless fails because Codecov is being rate limited. Source

This issue has been documented by others:
codecov/feedback#358
codecov/feedback#301
codecov/feedback#112

I've looked into this problem with #759. I think we will revert back to the bash uploader for now. I'm not sure if it's working properly but at least it doesn't fail the workflow. The bash uploader will be deprecated eventually but they will hopefully update their upload action by then.

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

Successfully merging a pull request may close this issue.

1 participant