-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comments
Resyncing the repo at coveralls did not fix this. |
I'm intermittently getting the same error
|
Same here. Had to detach a few builds from coveralls for now to bypass the issue which breaks them. |
I have the same issue here https://travis-ci.org/chrvadala/mqtt-dispatcher. |
Having the same issue, the last few days. On https://travis-ci.org/accordproject/cicero Restarting the build often works. |
@jeromesimeon restarting never works for me with this. |
@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. |
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. |
Getting similar here: https://travis-ci.org/zmckinnon/dice-tower
|
I've just started running into the same problem on my own builds. I've added a |
The situation has degenerated. I am now seeing 100% failure in this mode. |
@anjin @nickmerwin Is anyone home? |
there seems to be a general issue, it happens in all my repos, and also other people are having the same issue. |
@kortschak, Same here, 100% failures now. |
We are now investigating moving to codecov. |
Also getting failures for my public repo starting today. Yesterday was fine. |
Fix broken travis builds because of coveralls issue: lemurheavy/coveralls-public#1264
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... |
Hi guys, |
This seems to still be an issue on travis. |
same here - it stoped working |
Per #632 (comment), |
I also have this issue today:
|
Have this issue today: |
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. |
* 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
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.
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
This still seems to be an issue |
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. |
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.
Though other builds for the same PR succeed.
The text was updated successfully, but these errors were encountered: