-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Github action: uploading to coveralls fails since 2 December for version 1.9.1 with repo_token from env #211
Comments
jberends
changed the title
GITHUB action uploading to coveralls fails since 2 December for version 1.9.1 with repo_token from env
Dec 3, 2019
h
action uploading to coveralls fails since 2 December for version 1.9.1 with repo_token from env
jberends
changed the title
Github action: uploading to coveralls fails since 2 December for version 1.9.1 with repo_token from env
Dec 3, 2019
h
action uploading to coveralls fails since 2 December for version 1.9.1 with repo_token from env
#autoresolve In the mean time; a new release of coveralls was released to PyPI, while I was editing the issue and testing. Pinning python-coveralls on version 1.9.2 fixes the problem
|
Glad to hear its resolved -- thanks again to @ArturKlauser on #209 for the fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My github action seem to start failing at or around the time of the update of coveralls from 1.8.2 to 1.9.1.
Per the docs (which are a bit wonky here and there, see #206 ) we expose a
COVERALLS_REPO_TOKEN
being stored as a secret in the repositorty secrets (settings > secrets). The github action workflow can be found hereThis is the output of the last working example:
ref: https://github.com/KE-works/pykechain/runs/329621318
After the 2nd of december I get the following error across all branches.
coveralls debug
results inIt seems that the token is picket up correctly from the environment, but for some reason not used in the transfer to coveralls?
I also tested if github did change something to their secrets API or that github failed to expose the environment variables in the the shell, but those test pass successfully.
One remedy is to pin coveralls on 1.8.2 and that fixes the problem. Was there something changed in the coveralls package regarding github. I believe so when I look at the CHANGELOG
The text was updated successfully, but these errors were encountered: