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
Is your feature request related to a problem? Please describe.
Frequently enough to be frustrating, running coveralls fails in GitHub Actions due to an HTTP error. Retrying the Action run resolves this, but this can be painful for very long-running workflows.
Describe the solution you'd like
When API calls fail with transient HTTP error (e.g., bad gateway), they should be able to be retried (perhaps optionally, based on a CLI parameter) ideally with some kind of backoff.
Describe alternatives you've considered
implement retrying in the Action itself. Though, I'd rather not implement it in bash.
GitHub Actions doesn't implement any retry functionality itself like other CI providers, but retries might work in providers like GitLab.
To minimize the impact of the problem, I could use the artifact upload/download actions to move coverage reports from jobs to one place where they are transmitted. That way, when it fails, I just need to re-download the artifact and try the upload again, instead of running all the tests again. But it would be much better if the CLI could implement it.
Additional context
For example: this action run (which takes 9+ minutes to run!) ends with an error:
Traceback (most recent call last):
File "C:\hostedtoolcache\windows\Python\3.9.13\x64\lib\site-packages\coveralls\cli.py", line 98, in main
result = coverallz.wear()
File "C:\hostedtoolcache\windows\Python\3.9.13\x64\lib\site-packages\coveralls\api.py", line 275, in wear
return self.submit_report(json_string)
File "C:\hostedtoolcache\windows\Python\3.9.13\x64\lib\site-packages\coveralls\api.py", line 301, in submit_report
raise CoverallsException(
coveralls.exception.CoverallsException: Could not submit coverage: 504 Server Error: Gateway Time-out for url: https://coveralls.io/api/v1/jobs
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Frequently enough to be frustrating, running
coveralls
fails in GitHub Actions due to an HTTP error. Retrying the Action run resolves this, but this can be painful for very long-running workflows.Describe the solution you'd like
When API calls fail with transient HTTP error (e.g., bad gateway), they should be able to be retried (perhaps optionally, based on a CLI parameter) ideally with some kind of backoff.
Describe alternatives you've considered
Additional context
For example: this action run (which takes 9+ minutes to run!) ends with an error:
The text was updated successfully, but these errors were encountered: