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
Unable to upload report using coverage-reporter v0.6.8 #119
Comments
We're seeing this as well with our circleci integration. |
Same here using latest circleci orb coveralls/coveralls@2.2.1 |
Isn't ac469ac#diff-b07b49e9438f2f536ecc020f2c360f6afd54e56006bd7aa2b59cfff0a6338369R33 Tests don't fail because |
We have coverage in our requirements, and I just tested via shell to ensure coverage is present on the box and it is.
|
All, Thanks for the reports. We're working on an update that we hope to release shortly. I'll come back with an update. Thanks. |
The new parser fails for many people on CI because it requires a command-line tool that is proving tricky to guarantee installed and, if installed, tricky to guarantee we can find it. As a stopgap, revert that change and push that release out. The work in the commit is good, but we need to focus more on ensuring access to the command-line tool. This reverts commit ac469ac. Closes #119
I've reverted the coverage.py change that is leading to these errors, and cut release 0.6.9. I'm closing this issue, but please comment here if it's still a problem. |
Thanks, @mike-burns. If anyone's still having issues let us know. If it's urgent, feel free to email me at support@coveralls.io. |
|
I think that's something else
|
We're also experiencing this issue again. I opened a new issue: #124 |
All, just doing some housekeeping:
|
@afinetooth The |
What was wrong?
I'm not able to upload the report using the 0.6.8 version that was just released.
Logs
As we're still waiting for coverallsapp/github-action#170 I don't know if I have any options now using the github-action.
Please let me know if I need to provide any additional information around this, or if I can do something on my end to fix it.
The text was updated successfully, but these errors were encountered: