-
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
Randomly getting error 'Couldn't find a repository matching this job' #487
Comments
I'm getting this issue as well, about 1/6 builds. Since I have a matrix with 3 builds, that makes this extremely flaky. |
Some travis-ci builds throw error:
and |
@nickmerwin |
I have the same error. Are you working on a fix? |
Same thing here. Any news ? |
hi all, we're working on this now. Could one of you re-trigger a build for testing? Thanks! |
Still getting it over here :< |
Getting it here too. The interesting bit is that, when I go to "Updates" from the left nav, I see that the builds hit Coveralls but they're gray and have a question mark that, when hovered, says "No data" so I'm not sure what happened. Obviously it was able to find things on the Coveralls side and update it with something or those wouldn't exist. But they have no data. Seems like Coveralls got the request and failed to process it somehow? Don't know if it's related, but my Coveralls report was working fine until I pushed a tag (0.7.4 in my screenshot). Could just be a coincidence, but I figure it's worth mentioning. |
hi @victorquinn ok I found the issue -- your service_name parameter was coming in as "travis", as opposed to "travis-ci", which was tripping up our API. I've updated it to accept "travis" also now. Could you trigger another build? Thanks! |
That seemed to fix it! I can update my end to use "travis-ci" explicitly from here on if you need. I was under the impression that string was any string identifier; I did not know it had a set enumeration of values. Regardless, it would be nice in the future if the error message made a bit more sense. Thanks though @nickmerwin things look like they work! |
Still getting the error, and consistently, not randomly |
I am now also getting this error constantly, my last successful update was from 23 hours ago. I have tried this from both my work and home pcs, I also tried regenerating my tokens, all to no avail. I am using cpp-coveralls to handle the upload, last night (23 hours ago) this was working 'fine'. EDIT: I have tested and this happens across both the 2 repositories of mine that I tested. |
also got it here: https://travis-ci.org/tkoomzaaskz/json-schema-faker/builds/61471059 |
I just started getting this error on a previously working build. |
Hi guys we fixed an issue that should mitigate the 422 issue. Please try again now, thank you! |
Shall we bump the version or do something else? |
@tkoomzaaskz have you set up the repo on Coveralls yet? I don't see it here: https://coveralls.io/r/tkoomzaaskz/json-schema-faker |
It's working for me again. |
Thanks @nickmerwin 🎉 |
It is also working for me again. |
$ go get golang.org/x/tools/cmd/cover $ go test github.com/mantyr/goquery -covermode=count -coverprofile=123.cov I see https://github.com/mattn/goveralls and https://coveralls.zendesk.com/hc/en-us/articles/201342809-Go Tried to use: Tell me how it is run, please. |
cat ./.travis.yml go: before_install: script: This configuration returns: |
I still getting 422 error: |
Any update on this issue? I get it on either travis Push or travis PR randomly it seems: |
seeing this just now: |
@mweibel me too, seems to happen when both PR and PUSH jobs are submitting near the same time. I have added a |
@miigotu Could you please show an explicit example tox.ini with the positioning of that dash? thx |
Same thing there: |
This reverts commit 42ef656. LOL This randomly fails with: Bad response status from coveralls: 422 - {"message":"Couldn't find a repository matching this job.","error":true} And here shows that there's something real silly going on: lemurheavy/coveralls-public#487 So no, not worth the pain. $fancy--
Same thing for me: My CI starts 6 jobs, jobs 3 and 6 couldn't send to coveralls, I restarted manually job 3 and this time it worked fine. |
@nickmerwin This is clearly still an issue. Does it make sense to re-open this ticket? |
I have just started receiving this error as well. Ran manually twice and still getting the error. https://travis-ci.org/uptownhr/hackathon-starter-lite/builds/124082908 |
This error is still here. |
+1 , it's happened for me with last versions of python, coveralls |
Having this issue for html-to-react. |
It seems the problem is pyyaml or libyaml. Every project that used yaml in the code, will not working, for example: https://travis-ci.org/pylover/pymlconf/jobs/166512950 This issue must be open again |
The coveralls command just working fine on my local machine. But the same version is not working on travis box. |
I get this occasionally. Should I just my travis script sleep a bit and retry? |
For those who are also having this problem, using |
@nickmerwin could one of the causes be that two jobs in a build matrix try to upload coverage at the same time? |
No, I used a condition, which prevents concurrent uploads. |
|
I'm randomly getting this error for open source Node.js repo and travis-ci build:
Most of the time the connection goes well, but once in a while it fails with this error.
Here is full data of such incident: https://travis-ci.org/szwacz/fs-jetpack/jobs/56279033
Hint: as I seen the error happens with Node.js version 0.12, but never noticed it on version 0.10 (https://travis-ci.org/szwacz/fs-jetpack/builds/56279031).
The text was updated successfully, but these errors were encountered: