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

[kortschak]

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]

Resyncing the repo at coveralls did not fix this.

[jacktuck]

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}

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

[chrisgleissner]

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

[chrvadala]

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

[jeromesimeon]

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

[kortschak]

@jeromesimeon restarting never works for me with this.

[jeromesimeon]

@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]

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]

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]

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]

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

[kortschak]

@anjin @nickmerwin Is anyone home?

[alvarolorentedev]

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]

@kortschak, Same here, 100% failures now.

[kortschak]

We are now investigating moving to codecov.

[sb10]

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

[Ismaestro]

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]

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]

This seems to still be an issue on travis.

[bkielbasa]

same here - it stoped working

[afinetooth]

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

[ndelvalle]

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]

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

[afinetooth]

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.

[binarymist]

This still seems to be an issue

[afinetooth]

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.