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

"Couldn't find a repository matching this job." status 422 for public repo #1264

Closed
kortschak opened this issue Feb 17, 2019 · 35 comments
Closed

Comments

@kortschak
Copy link

Today I have seen a series of Coveralls build failures for a public repository with CI builds being done by Travis-CI. This appears to be a long standing recurrent issue #715, #408, #984 etc.

Travis-CI log for build.

Bad response status from coveralls: 422
{"message":"Couldn't find a repository matching this job.","error":true}

Though other builds for the same PR succeed.

@kortschak
Copy link
Author

Resyncing the repo at coveralls did not fix this.

@jacktuck
Copy link

jacktuck commented Feb 17, 2019

I'm intermittently getting the same error

/home/travis/build/jacktuck/unfurl/node_modules/coveralls/bin/coveralls.js:18
        throw err;
        ^
Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true}

image

https://travis-ci.org/jacktuck/unfurl/jobs/494500772

@chrisgleissner
Copy link

Same here. Had to detach a few builds from coveralls for now to bypass the issue which breaks them.

@chrvadala
Copy link

I have the same issue here https://travis-ci.org/chrvadala/mqtt-dispatcher.

@jeromesimeon
Copy link

Having the same issue, the last few days. On https://travis-ci.org/accordproject/cicero Restarting the build often works.

@kortschak
Copy link
Author

@jeromesimeon restarting never works for me with this.

@jeromesimeon
Copy link

@kortshack Thanks. It might be a different issue then, but the symptoms are the same and it started a few days ago. Definitely intermittent for us.

@kortschak
Copy link
Author

Yeah, I don't doubt it's the same cause. I don't understand how the differences arise. My approach for now is to just make the coveralls failure a warning event rather than an error event.

@zmckinnon
Copy link

Getting similar here: https://travis-ci.org/zmckinnon/dice-tower

Failed to upload to coveralls
UnprocessableEntity - Couldn't find a repository matching this job.

@srepollock
Copy link

srepollock commented Feb 19, 2019

I've just started running into the same problem on my own builds. I've added a COVERALLS_REPO_TOKEN with my API key as an environment variable with Travis to keep it secure, yet I'm still getting the same issue. Is there another token name that Coveralls looks for? I'm trying not to put the token in plain text and commit it...

@kortschak
Copy link
Author

The situation has degenerated. I am now seeing 100% failure in this mode.

@kortschak
Copy link
Author

@anjin @nickmerwin Is anyone home?

@alvarolorentedev
Copy link

there seems to be a general issue, it happens in all my repos, and also other people are having the same issue.
nickmerwin/node-coveralls#166

@ericmorand
Copy link

@kortschak, Same here, 100% failures now.

@kortschak
Copy link
Author

We are now investigating moving to codecov.

@sb10
Copy link

sb10 commented Feb 19, 2019

Also getting failures for my public repo starting today. Yesterday was fine.

mischah added a commit to micromata/generator-baumeister that referenced this issue Feb 20, 2019
Fix broken travis builds because of coveralls issue: lemurheavy/coveralls-public#1264
@Ismaestro
Copy link

This is happening right now again. @nickmerwin that is cool, but maybe we should think in a more proper way to avoid this problem in the future...

@victkarangwa
Copy link

Hi guys,
I solved this issue by updating COVERALLS_REPO_TOKEN in .circleci/config.yml.
You can check if COVERALLS_REPO_TOKEN you are having is the same as the one generated by coveralls.io.

@estroz
Copy link

estroz commented May 22, 2020

This seems to still be an issue on travis.

@bkielbasa
Copy link

same here - it stoped working

@afinetooth
Copy link
Collaborator

Per #632 (comment),
we think the recent occurrence is a GitHub issue: https://www.githubstatus.com/

@ndelvalle
Copy link

I also have this issue today:

Bad response: 422 {"message":"service_job_id (340775507) must be unique for Travis Jobs not supplying a Coveralls Repo Token","error":true}

@Lucasjuv
Copy link

Have this issue today:
{"message":"service_job_id (375382350) must be unique for Travis Jobs not supplying a Coveralls Repo Token","error":true}

@afinetooth
Copy link
Collaborator

Hi @Lucasjuv per my comment here, if you want to email us a support@coveralls.io with the link to your coveralls project, we'll look into it further for you.

german1608 added a commit to t-creo/back-end that referenced this issue Sep 24, 2020
* fix error of coveralls by moving coverage uploading to after_success

(see lemurheavy/coveralls-public#1264)

* add mock .env file

* add scripts to analyze times

* remove unnecessary async functions

* rename analyze_times.js -> analyzeTimes.js

* add scripts to measure text credibility execution times

* s/World White Web/T-CREo
goretkin added a commit to goretkin/FixArgs.jl that referenced this issue Nov 9, 2020
Coveralls is causing the workflow to fail with
"Couldn't find a repository matching this job."

lemurheavy/coveralls-public#1264 (comment)
Not sure what's happening here. I had only just now created a corresponding project on codecov for this repo.
thezimmee pushed a commit to brikcss/merge that referenced this issue Feb 21, 2021
SaiedKazemi pushed a commit to m-lab/traceroute-caller that referenced this issue May 11, 2021
Recent Travis CI builds have been failing due to coveralls
failures with an error message like this:

  Bad response status from coveralls: 422
  {"message":"service_job_id (504405309) must be unique for \
  Travis Jobs not supplying a Coveralls Repo Token","error":true}

This is a known issue, and we're using the suggested workaround:
lemurheavy/coveralls-public#1264
exbotanical added a commit to exbotanical/vivisector that referenced this issue Sep 9, 2021
@binarymist
Copy link

This still seems to be an issue

@afinetooth
Copy link
Collaborator

Hi @binarymist. There are different causes for these different 422 results, so it would be ideal to cover them in separate issues dedicated to each root cause.

In your case, is this happening after you've migrated from Travis CI to Github Actions?

If not, what is your use case? And what is the message that comes along with your 422 status code?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests