You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: