Randomly getting error 'Couldn't find a repository matching this job' #487

szwacz · 2015-03-29T08:28:57Z

I'm randomly getting this error for open source Node.js repo and travis-ci build:

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

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:

TheSavior · 2015-04-08T06:13:51Z

I'm getting this issue as well, about 1/6 builds. Since I have a matrix with 3 builds, that makes this extremely flaky.

s0ph1e · 2015-04-25T14:31:55Z

Some travis-ci builds throw error:

/home/travis/build/s0ph1e/node-css-url-parser/node_modules/coveralls/bin/coveralls.js:18
        throw err;
              ^
Bad response: 504 <!DOCTYPE html>
<html lang="en">
  <head>
<meta http-equiv="refresh" content="0">
<meta http-equiv="set-cookie" content="cf_use_ob=443; expires=Sat, 25-Apr-15 14:24:25 GMT; path=/">
<meta http-equiv="set-cookie" content="cf_ob_info=504:1dcab4a4a2ab0856:IAD; expires=Sat, 25-Apr-15 14:24:25 GMT; path=/">
    <meta charset="utf-8" />
    <meta content="IE=Edge,chrome=1" http-equiv="X-UA-Compatible" />
    <title>Coveralls :: Oops, something went wrong (500)</title>

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

s0ph1e · 2015-04-25T14:45:39Z

@nickmerwin
I started receiving 500 error randomly for my packages.
https://travis-ci.org/s0ph1e/node-website-scraper/jobs/59368954
https://travis-ci.org/s0ph1e/node-css-url-parser/jobs/60011110

lukasoppermann · 2015-05-03T08:05:36Z

I have the same error. Are you working on a fix?

nlamirault · 2015-05-05T11:58:28Z

Same thing here. Any news ?

nickmerwin · 2015-05-05T16:58:51Z

hi all, we're working on this now. Could one of you re-trigger a build for testing?

Thanks!

koddsson · 2015-05-05T19:52:33Z

Still getting it over here :<

victorquinn · 2015-05-05T20:09:36Z

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.

nickmerwin · 2015-05-05T21:06:22Z

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!

victorquinn · 2015-05-05T21:31:10Z

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!

kunalgolani · 2015-05-06T08:11:25Z

Still getting the error, and consistently, not randomly

chrisosaurus · 2015-05-06T09:30:15Z

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.

ducin · 2015-05-06T14:28:52Z

also got it here: https://travis-ci.org/tkoomzaaskz/json-schema-faker/builds/61471059

jessamynsmith · 2015-05-06T16:17:18Z

I just started getting this error on a previously working build.
https://circleci.com/gh/jessamynsmith/taotrack

nickmerwin · 2015-05-06T17:59:46Z

Hi guys we fixed an issue that should mitigate the 422 issue. Please try again now, thank you!

ducin · 2015-05-06T19:59:43Z

Shall we bump the version or do something else?

nickmerwin · 2015-05-06T20:00:48Z

@tkoomzaaskz have you set up the repo on Coveralls yet? I don't see it here: https://coveralls.io/r/tkoomzaaskz/json-schema-faker

jessamynsmith · 2015-05-07T14:03:44Z

It's working for me again.

koddsson · 2015-05-07T14:06:44Z

Thanks @nickmerwin 🎉

chrisosaurus · 2015-05-07T22:06:37Z

It is also working for me again.

mantyr · 2015-06-12T18:29:12Z

$ go get golang.org/x/tools/cmd/cover
$ go get github.com/mattn/goveralls
$ go install github.com/mattn/goveralls

$ go test github.com/mantyr/goquery -covermode=count -coverprofile=123.cov
ok github.com/mantyr/goquery 0.025s coverage: 85.7% of statements
$ /usr/gobin/goveralls -coverprofile=123.cov -service=travis-ci
Bad response status from coveralls: 422 - {"message":"Couldn't find a repository matching this job.","error":true}

I see https://github.com/mattn/goveralls and https://coveralls.zendesk.com/hc/en-us/articles/201342809-Go

Tried to use:
-repotoken
-service = travis-ci
-service = travis

Tell me how it is run, please.

mantyr · 2015-06-12T21:58:43Z

cat ./.travis.yml
language: go

go:
- 1.1
- 1.2
- 1.3
- 1.4
- tip

before_install:
- go get github.com/axw/gocov/gocov
- go get github.com/mattn/goveralls
- if ! go get code.google.com/p/go.tools/cmd/cover; then go get golang.org/x/tools/cmd/cover; fi

script:
- $HOME/gopath/bin/goveralls -service=travis-ci

This configuration returns:
Bad response status from coveralls: 500 - {"message":"Build processing error.","error":true,"url":""}
The command "$HOME/gopath/bin/goveralls -service=travis-ci" exited with 1.

aivus · 2015-07-15T08:32:21Z

I still getting 422 error:
https://travis-ci.org/s0ph1e/node-website-scraper/jobs/71037428

…lls-public#487

ChristopherRabotin · 2015-09-30T10:15:37Z

Any update on this issue? I get it on either travis Push or travis PR randomly it seems:

iamqizhao · 2015-10-08T21:49:59Z

seeing this just now:
https://travis-ci.org/grpc/grpc-go

miigotu · 2016-04-12T16:39:36Z

@mweibel me too, seems to happen when both PR and PUSH jobs are submitting near the same time. I have added a - to the beginning of the coveralls line in my tox.ini so it submits when it succeeds but doesnt fail the build if coveralls fails to submit.

michaelaye · 2016-04-12T16:48:28Z

@miigotu Could you please show an explicit example tox.ini with the positioning of that dash? thx

miigotu · 2016-04-12T17:43:44Z

https://github.com/SickRage/SickRage/blob/master/tox.ini#L17

gilles-duboscq · 2016-04-13T15:57:59Z

Same thing there:
https://travis-ci.org/chimpler/pyhocon/builds/122821766
2 jobs worked and 2 jobs failed
https://github.com/chimpler/pyhocon/blob/master/tox.ini

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

touilleMan · 2016-04-18T14:01:41Z

Same thing for me:
https://travis-ci.org/Scille/umongo/jobs/123910062#L375

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.

TheSavior · 2016-04-18T17:16:14Z

@nickmerwin This is clearly still an issue. Does it make sense to re-open this ticket?

uptownhr · 2016-04-19T03:13:19Z

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

vitalyisaev2 · 2016-10-07T11:48:07Z

This error is still here.

pylover · 2016-10-07T17:05:52Z

+1 , it's happened for me with last versions of python, coveralls

aknuds1 · 2016-10-15T12:59:43Z

Having this issue for html-to-react.

pylover · 2016-10-16T08:04:06Z

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

pylover · 2016-10-16T20:06:46Z

The coveralls command just working fine on my local machine. But the same version is not working on travis box.

cce · 2016-10-17T23:15:49Z

I get this occasionally. Should I just my travis script sleep a bit and retry?

cce · 2016-10-18T01:38:22Z

For those who are also having this problem, using travis_retry seems to help as in: thriftrw/thriftrw-go#69

jedwards1211 · 2017-04-12T23:35:23Z

@nickmerwin could one of the causes be that two jobs in a build matrix try to upload coverage at the same time?

pylover · 2017-04-15T19:51:50Z

No, I used a condition, which prevents concurrent uploads.

pylover · 2017-04-15T20:08:07Z

5.44s$ if [[ $TRAVIS_PYTHON_VERSION == '3.5' ]]; then travis_retry coveralls ; fi
Submitting coverage to coveralls.io...
Coverage submitted!
Couldn't find a repository matching this job.
'url'
The command "coveralls" failed. Retrying, 2 of 3.
Submitting coverage to coveralls.io...
Coverage submitted!
Couldn't find a repository matching this job.
'url'
The command "coveralls" failed. Retrying, 3 of 3.
Submitting coverage to coveralls.io...
Coverage submitted!
Couldn't find a repository matching this job.
'url'
The command "coveralls" failed 3 times.

mirismaili · 2019-06-29T10:52:33Z

Similar issue:

Jub 45:

/home/circleci/.npm/_npx/845/lib/node_modules/coveralls/bin/coveralls.js:18
        throw err;
        ^
Bad response: 500 {"message":"Build processing error.","error":true,"url":""}
Exited with code 1

Restarting the job without any change:

Jub 46: OK

aivus mentioned this issue Apr 27, 2015

Revert "Add coveralls.io support" website-scraper/node-website-scraper#7

Merged

ducin mentioned this issue May 6, 2015

Extending low-level dependencies json-schema-faker/json-schema-faker#12

Closed

nickmerwin closed this as completed May 6, 2015

mantyr mentioned this issue Jun 12, 2015

Getting "Build processing error" #547

Closed

hackhat pushed a commit to hackhat/smart-css that referenced this issue Jul 19, 2015

Travis has some issues and keeps failing the build: lemurheavy/covera…

1178ae2

…lls-public#487

jacquerie mentioned this issue Apr 19, 2016

WIP tests: more integration tests inspirehep/inspire-next#1053

Closed

jfirebaugh mentioned this issue Apr 20, 2016

Ensure CI builds for branches in 3rd party repositories build successfully mapbox/mapbox-gl-js#2465

Closed

ahelmberger mentioned this issue May 26, 2016

Calculate ignoring time and timezone values jdiehl/holiday-de#1

Merged

JoeCostanzo mentioned this issue Jun 2, 2016

Coveralls dep is a smell SEAPUNK/socketeer#77

Closed

lucaslago mentioned this issue Mar 29, 2017

Setup dockerized tests agco/harvesterjs#207

Merged

5 tasks

pylover added a commit to pylover/pymlconf that referenced this issue Apr 15, 2017

Coverals, lemurheavy/coveralls-public#487

97c8499

pylover added a commit to pylover/pymlconf that referenced this issue Apr 15, 2017

Coveralls, travis_retry, lemurheavy/coveralls-public#487

074507f

blueyed mentioned this issue Oct 3, 2017

Circle-CI: Couldn't find a repository matching this job. #1018

Closed

jcfr mentioned this issue Mar 5, 2019

Test against Python 3.7 and support pytest 4.x man-group/pytest-plugins#130

Closed

mirismaili mentioned this issue Jun 29, 2019

"Build processing error" when submitting merged coverage file #548

Closed

fabOnReact mentioned this issue Dec 31, 2019

Allow touches on overflowed children when overflow: visible (Android) facebook/react-native#26374

Closed

Randomly getting error 'Couldn't find a repository matching this job' #487

Randomly getting error 'Couldn't find a repository matching this job' #487

Comments

szwacz commented Mar 29, 2015

TheSavior commented Apr 8, 2015

s0ph1e commented Apr 25, 2015

s0ph1e commented Apr 25, 2015

lukasoppermann commented May 3, 2015

nlamirault commented May 5, 2015

nickmerwin commented May 5, 2015

koddsson commented May 5, 2015

victorquinn commented May 5, 2015

nickmerwin commented May 5, 2015

victorquinn commented May 5, 2015

kunalgolani commented May 6, 2015

chrisosaurus commented May 6, 2015

ducin commented May 6, 2015

jessamynsmith commented May 6, 2015

nickmerwin commented May 6, 2015

ducin commented May 6, 2015

nickmerwin commented May 6, 2015

jessamynsmith commented May 7, 2015

koddsson commented May 7, 2015

chrisosaurus commented May 7, 2015

mantyr commented Jun 12, 2015

mantyr commented Jun 12, 2015

aivus commented Jul 15, 2015

ChristopherRabotin commented Sep 30, 2015

iamqizhao commented Oct 8, 2015

miigotu commented Apr 12, 2016

michaelaye commented Apr 12, 2016

miigotu commented Apr 12, 2016

gilles-duboscq commented Apr 13, 2016

touilleMan commented Apr 18, 2016

TheSavior commented Apr 18, 2016

uptownhr commented Apr 19, 2016 • edited Loading

vitalyisaev2 commented Oct 7, 2016

pylover commented Oct 7, 2016

aknuds1 commented Oct 15, 2016

pylover commented Oct 16, 2016 • edited Loading

pylover commented Oct 16, 2016

cce commented Oct 17, 2016

cce commented Oct 18, 2016

jedwards1211 commented Apr 12, 2017

pylover commented Apr 15, 2017

pylover commented Apr 15, 2017

mirismaili commented Jun 29, 2019

uptownhr commented Apr 19, 2016 •

edited

Loading

pylover commented Oct 16, 2016 •

edited

Loading