-
Notifications
You must be signed in to change notification settings - Fork 0
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
Travis failing to publish code coverage to Coveralls #33
Comments
After some research I found the following:
|
j-richey
added a commit
that referenced
this issue
May 31, 2020
The build was using the cargo-travis along with kcov to generate coverage data and submit it to coveralls. Unfortunately, this stopped working due to a Rust update (roblabla/cargo-travis#66). Additionally, it was difficult to run this tool locally. This commit uses cargo-tarpaulin to generate the test coverage data and upload it to coveralls. Additionally, developers with Linux can easily generate coverage reports locally with tarpaulin. The CONTRIBUTING file is updated with instructions on how to generate coverage reports. See issue #33.
The project has been updated to use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Travis has stopped sending code coverage reports to Coveralls. This was noticed when creating the v0.1.2 release.
First, the job that pushes the code coverage report was not appearing in the build matrix. After a bit of hacking to get it to appear in the matrix and get the job to run there was a problem with the
cargo coveralls
command:Steps to reproduce
jobs/exclude
keys and push the change.Library Version:
Use the
.travis.yaml
from0.1.2
build was used.Expected behavior
Code coverage should be generated with every Travis build.
Additional context
Here is a resource that might be useful when debugging
.travis.yaml
file issues: https://config.travis-ci.com/exploreThe text was updated successfully, but these errors were encountered: