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

Getting 422 Unprocessable Entity when uploading from AppVeyor #1392

Closed
morozov opened this issue Jan 4, 2020 · 2 comments
Closed

Getting 422 Unprocessable Entity when uploading from AppVeyor #1392

morozov opened this issue Jan 4, 2020 · 2 comments
Labels
4xx-error marked-for-closure potential-bug potential bug as reported, needs reproduced. set-up setup issues

Comments

@morozov
Copy link

morozov commented Jan 4, 2020

This is an exceprt from the failing build:

Submitting to https://coveralls.io/api/v1/jobs
Client error occurred. status: 422 Unprocessable Entity
Couldn't find a repository matching this job.

I'm trying to use php-coveralls to upload the coverage report which seems to support AppVeyor out of the box:

Set environment variables properly like the following.

For AppVeyor users:

  - APPVEYOR
  - APPVEYOR_BUILD_NUMBER

Assuming that this message is not displayed on AppVeyor, it picks up the environment correctly.

Using the same uploader in the same repository, I can upload the report from the local environment:

$ wget https://github.com/php-coveralls/php-coveralls/releases/latest/download/php-coveralls.phar
$ phpunit  --coverage-clover build/logs/clover.xml
$ export COVERALLS_RUN_LOCALLY=1
$ export COVERALLS_REPO_TOKEN=********
$ php php-coveralls.phar -v

Finish submitting. status: 200 OK
Accepted Job ##3229.1
You can see the build on https://coveralls.io/jobs/57424597

Is there something I'm missing in the configuration? Thanks.

@afinetooth afinetooth added potential-bug potential bug as reported, needs reproduced. set-up setup issues labels Apr 3, 2020
@afinetooth afinetooth added this to potential-bug in Labeled Issues Apr 14, 2020
@peter-gribanov
Copy link

I have a similar problem in Travis CI. Is there any solution?

@stale
Copy link

stale bot commented Oct 1, 2021

This issue has been automatically marked for closure because it has not had recent activity. It will be closed if no further activity occurs. If your issue is still active please add a comment and we’ll review as soon as we can. Thank you for your contributions.

@stale stale bot closed this as completed Oct 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4xx-error marked-for-closure potential-bug potential bug as reported, needs reproduced. set-up setup issues
Projects
Labeled Issues
potential-bug
Development

No branches or pull requests

3 participants