Skip to content
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." - CircleCI + nyc + mocha #277

Open
piotr-s-brainhub opened this issue Mar 10, 2020 · 5 comments

Comments

@piotr-s-brainhub
Copy link

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

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
Copy link
Owner

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

@rook2pawn
Copy link

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

@piotr-s-brainhub
Copy link
Author

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

afinetooth commented Oct 30, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants