-
Notifications
You must be signed in to change notification settings - Fork 13
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
Coverage reported as 0% when using cargo test --all
#5
Comments
Looking into it |
https://travis-ci.org/Hoverbear/rust-rosetta/builds/205573979#L4329 Cargo coveralls isn't running any tests :| |
could you try |
Build log with |
So at least this time it ran the tests. The problem is, kcov seems to choke when trying to open some directories. I cloned your repo and managed to reproduce the issue. I'll play around with it and report back when I get it to work :). |
So this problem is due to the way workspaces work. The "target" directory isn't next to the cwd() in this case. I'm refactoring the code to use cargo methods to recover the location of the "target" directory. This should be much more robust, and allow it to also support things like |
0.0.3 is published on crates.io. If you run the builds again, it should work. |
Ah, thank you for the quick work! It recorded coverage, but also took the coverage of some library dependencies (...? I see glium, glutin etc. in the covered files). So, it's giving incorrect coverage. Coverage log here: https://coveralls.io/builds/10337936 |
You're right. It seems that it's more problems with workspaces. I'm investigating. |
Fixed with 2581789 . 0.0.4 released. |
Woops. This wasn't quite fixed, and I forgot to reopen it. https://coveralls.io/builds/10347968 It's really weird, coveralls seems eager to include files that are not in the include-path. I need to investigate this more. I'll try to go over it this week-end. |
See report here: rust-rosetta/rust-rosetta#563
The text was updated successfully, but these errors were encountered: