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. #1268

Closed
leeqvip opened this issue Feb 19, 2019 · 9 comments
Closed

Couldn't find a repository matching this job. #1268

leeqvip opened this issue Feb 19, 2019 · 9 comments

Comments

@leeqvip
Copy link

leeqvip commented Feb 19, 2019

$ $HOME/gopath/bin/goveralls -service=travis-ci
Bad response status from coveralls: 422
{"message":"Couldn't find a repository matching this job.","error":true}
The command "$HOME/gopath/bin/goveralls -service=travis-ci" exited with 1.

@MrSwitch
Copy link

MrSwitch commented Feb 19, 2019

This has occurred for me since ~14 to 20 hours ago.

@MrSwitch
Copy link

Duplicate of #1264

@nickmerwin
Copy link
Member

Hi @techoner, turned out we had our webserver IPs accidentally blacklisted by Travis, so we couldn't query their API to get job info as coverage data was posted.

Apologies for the gap in service here! We're adding failsafes to warn us early about this in the future.

@piyushpyoaknorth
Copy link

piyushpyoaknorth commented Nov 18, 2019

Hi,
I am seeing this error too. It worked a couple of time, and then started failing with this error.

I tried

  1. Re-synching the repositories, which fails.
  2. Added the .coverall.yml file

But still does not seem to resolve this issue.

This happens only when I give the path to base_directory, while using the python-coveralls library

@mohawk2
Copy link

mohawk2 commented Nov 5, 2020

I am seeing this error from GitHub Actions (though not from Travis):

On another repo (https://github.com/graphviz-perl/GraphViz2/runs/1350929974) I tried the advice in #1264 of deleting and reenabling on coveralls.io, which didn't help. Doing the coveralls update on my local machine, giving the correct token, worked.

Advise please?

@afinetooth
Copy link
Collaborator

afinetooth commented Nov 5, 2020

Hi @mohawk2, the Github Action is a little different. The Action provides an access token that we leverage instead of the repo_token. It's fine to add that, but the Action is looking for its token, which should be setup in your workflow file as follows:

[...]
- name: Coveralls
uses: coverallsapp/github-action@master
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
[...]

Reference here:
https://github.com/marketplace/actions/coveralls-github-action#standard-example

It looks like you're setting secrets.GITHUB_TOKEN to the env var, but for the Action, the relevant parameter is github-token.

Hope that works for you.

@afinetooth
Copy link
Collaborator

@mohawk2 On a second look, I realize you may be doing this without the use of the Coveralls Github Action.

In that case, you'll want to set the env var COVERALLS_REPO_TOKEN to the real repo_token from your project start page, rather than the github token.

Try that and let us know.

@mohawk2
Copy link

mohawk2 commented Nov 5, 2020

@afinetooth Thanks! I created a particular secret called COVERALLS_TOKEN per instructions in https://docs.github.com/en/free-pro-team@latest/actions/reference/encrypted-secrets with the repo token on the relevant coveralls.io page (https://coveralls.io/github/graphviz-perl/GraphViz2), then referenced it in my GH action. It now works.

I will feed this back to the author of the Perl Coveralls reporting module to update the docs.

However, the message is terrible because it's misleading. PLEASE get this switched so it says something that indicates "right repo, wrong auth". That's a lot of time I lost because someone was lazy with their error-reporting.

@mohawk2
Copy link

mohawk2 commented Nov 8, 2020

Thanks to kan/coveralls-perl#33 there is now working coverage-reporting for Perl with no need for making the Coveralls secret.

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

6 participants