feat: use llvm-cov for coverage#478
Conversation
Wodann
left a comment
There was a problem hiding this comment.
I'm curious to see whether there is a performance overhead compared to nextest
Codecov Report
@@ Coverage Diff @@
## main #478 +/- ##
==========================================
+ Coverage 79.31% 87.16% +7.85%
==========================================
Files 256 271 +15
Lines 13496 29356 +15860
==========================================
+ Hits 10704 25588 +14884
- Misses 2792 3768 +976
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
Looks like its working properly! Except on windows. I figured that llvm-cov is using another cargo profile which I have to make sure is also used during doctesting, otherwise the build will take much longer and disc space will run out. |
|
The dreaded out of storage issue is back 😢 Did you still have options to try to reduce storage usage? Can we split main tests vs example tests? |
Yeah! I already have an idea as outlined in the comment above! |
|
@Wodann It works! Finally! |
Use llvm-cov instead of tarpauling to compute coverage. LLVM-cov uses recently stabilized code coverage metrics emitted by the rust compiler. This also then works on Windows and MacOS and can be collected while running the regular tests.
I did have to change some tests to no longer use the name of the thread that is executing the tests. This is because that behavior (which was unstable in the first place) doesn't work with llvm-cov.