nickmerwin / node-coveralls

lcov posting to coveralls.io
Other
1.07k stars 258 forks source link

"Couldn't find a repository matching this job." - CircleCI + nyc + mocha #277

Open piotr-s-brainhub opened 4 years ago

piotr-s-brainhub commented 4 years ago

I get this error:

yarn coverage
yarn run v1.22.0
$ nyc report --reporter=text-lcov | coveralls

/home/circleci/app/node_modules/coveralls/bin/coveralls.js:19
      throw err;
      ^
Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true}
(Use `node --trace-uncaught ...` to show where the exception was thrown)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Exited with code exit status 1

in https://circleci.com/gh/brainhubeu/tdd-js/46

rook2pawn commented 4 years ago

I'm getting the exact same error as well.

npm test && nyc report --reporter=text-lcov | coveralls

 "coveralls": "^3.1.0",
 "nyc": "^13.1.0",
nickmerwin commented 4 years ago

hei @piotr-s-brainhub and @rook2pawn, could you please run your build with coveralls --verbose and link me to the output?

rook2pawn commented 4 years ago

output from npm test && nyc report --reporter=text-lcov | coveralls --verbose https://curlpaste.com/web/mnk7ge

piotr-s-brainhub commented 4 years ago

Now it works for me.

I have:

echo repo_token: $COVERALLS_REPO_TOKEN > ./.coveralls.yml
cat ./coverage/lcov.info | ./node_modules/coveralls/bin/coveralls.js

I guess the error was because of not adding the repo to coveralls.

afinetooth commented 4 years ago

@rook2pawn i was just reviewing this before closing. i looked at your verbose output here: above:https://curlpaste.com/web/mnk7ge

FWIW, the issue appears to be your repo_token.

This is an unlikely value: Screen Shot 2020-10-30 at 3 10 43 PM

I believe if you remove the "TOKEN" prefix, you'll stop getting the 422 error.