Skip to content

Commit

Permalink
Ignore coveralls upload failures
Browse files Browse the repository at this point in the history
I am once again seeing

    Submitting coverage to coveralls.io...
    Could not submit coverage: 422 Client Error: Unprocessable Entity for url: https://coveralls.io/api/v1/jobs
    resubmitting with id None
    Traceback (most recent call last):
      File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/site-packages/coveralls/api.py", line 290, in submit_report
        response.raise_for_status()
      File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/site-packages/requests/models.py", line 1021, in raise_for_status
        raise HTTPError(http_error_msg, response=self)
    requests.exceptions.HTTPError: 422 Client Error: Unprocessable Entity for url: https://coveralls.io/api/v1/jobs

    The above exception was the direct cause of the following exception:

    Traceback (most recent call last):
      File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/site-packages/coveralls/cli.py", line 95, in main
        result = coverallz.wear()
      File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/site-packages/coveralls/api.py", line 257, in wear
        return self.submit_report(json_string)
      File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/site-packages/coveralls/api.py", line 293, in submit_report
        raise CoverallsException(
    coveralls.exception.CoverallsException: Could not submit coverage: 422 Client Error: Unprocessable Entity for url: https://coveralls.io/api/v1/jobs
    Error: Process completed with exit code 1.

when nothing has changed in my repo or configuration.

I've had enough of coveralls.  If the numbers fail to upload, so be it.
  • Loading branch information
mgedmin committed May 2, 2023
1 parent 5277fd6 commit b3d1d96
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions .github/workflows/build.yml
Expand Up @@ -60,6 +60,7 @@ jobs:

- name: Report to coveralls
run: coveralls
continue-on-error: true
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
COVERALLS_SERVICE_NAME: github
Expand Down

1 comment on commit b3d1d96

@toonarmycaptain
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thankyou for this; I've been plagued by the 422 in a bunch of repos and am now just making the report a separate step with continue-on-error

Please sign in to comment.