-
Notifications
You must be signed in to change notification settings - Fork 220
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
Code coverage using cargo-travis on coveralls. #265
Conversation
https://travis-ci.org/slide-rs/specs/jobs/276531441#L2188 :
Should we do anything about that? |
I have created issue to It seems to work fine for my project so I don't know if it's actually a problem. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
I added the repo to coveralls.
I suppose squashing the 2 commits wouldn't hurt before merging ;)
Good idea. It also tests that my change actually sends the coverage to coveralls. |
Changes Unknown when pulling 1b2a2c1 on WaDelma:coverage into ** on slide-rs:master**. |
You should remove those coveralls messages (I don't know why they are on by default). Also the coverage report doesn't open the files because it has empty prefix and it should be changed to |
90%? That's much more than I expected. |
Btw, why remove the coveralls messages? |
It creates after every CI round. So if you push 10 commits in rapid succession it will spam 10 messages to the PR. |
Oh I see. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So.. I think we can merge this?
Thank you @WaDelma! bors r+ |
Build succeeded |
This PR adds automatic code coverage testing using
cargo-travis
andcoveralls
.Note: I cannot add the repo to coveralls as I am not member of the github organization.