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

Supply Repo Token when reporting test coverage to coveralls.io #228

Closed
liangyuanruo opened this issue Aug 28, 2020 · 2 comments
Closed

Supply Repo Token when reporting test coverage to coveralls.io #228

liangyuanruo opened this issue Aug 28, 2020 · 2 comments

Comments

@liangyuanruo
Copy link
Contributor

Duplicate service job IDs from Travis during job restarts cannot pass CI due to coveralls.io error. The existing workaround is to manually trigger a new job instead of restarting an existing one.

Bad response: 422 {"message":"service_job_id (378233677) must be unique for Travis Jobs not supplying a Coveralls Repo Token","error":true}

Introduce a Coveralls repo token so that jobs can be easily restarted.

@liangyuanruo liangyuanruo added P2 planned for next 1-2 months tech debt reliability labels Aug 28, 2020
@arshadali172 arshadali172 self-assigned this Sep 9, 2020
@arshadali172
Copy link
Contributor

arshadali172 commented Sep 10, 2020

Tried 3 possible solutions:

  1. Specifying COVERALLS_REPO_TOKEN as suggested here and documented here. Though, multiple comments say that a token should not even need to be specified for public repos.

  2. Moving the coveralls script to after_success as suggested here.

  3. Explicitly specifying the COVERALLS_SERVICE_JOB_ID as suggested here.

None worked. There are some suggestions to move to codeCov, which I suggest that we explore.

@arshadali172 arshadali172 removed their assignment Oct 12, 2020
@liangyuanruo liangyuanruo added P3 and removed P2 planned for next 1-2 months labels Mar 8, 2021
@r00dgirl r00dgirl added P4 and removed P3 labels Mar 10, 2021
@tshuli
Copy link
Contributor

tshuli commented Sep 15, 2023

Stale

@tshuli tshuli closed this as completed Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants