-
In GitLab by @yvan-sraka
_Merges yvan-sraka-dev-patch-86993 -> dev_
https://crates.io/crates/cargo-tarpaulin#gitlab-pipelines
-
I followed the manual from README, both `.profraw` and `.gcda`. And then I try to run following command to generate coverage report have the same panic
```
grcov . -s . --binary-path ./target/debu…
-
with `torch-sys` in cargo deps by default if torch is not installed system-wide cargo will build and install libtorch by itself somewhere to `target/` and application if run with `cargo run` will find…
-
Tarpaulin relies on signals to get code coverage: https://github.com/xd009642/tarpaulin#note-on-tests-using-signals
Wasmer also relies on these signals for various things. We're currently working …
-
**Describe the bug**
I have a relatively small application that has just a couple of simple unit tests. I noticed that when I was trying to get my CI to start procuding JUnit and coverage XMLs I …
-
-
Seems like it's supported:
https://github.com/rust-lang/rust/issues/34701#issuecomment-753125299
Possible integration:
https://github.com/marketplace/actions/rust-grcov
-
How timeout could be a correctness concept? Is the code could still be correct but fail tests with relaxed timeout?
Timeout are for performance measuring or fail early, if our timeout values just m…
-
**Describe the bug**
cobertura xml line rate differs from the reported coverage in the console output. I though perhaps this is because it is including the coverage for the examples folder. I have t…
-
Currently the test-coverage is broken.
This is due to incompatibility between `bitvec 0.19.5` and cargo-tarpaulin. While most packages depend on bitvec "0.20.*", which is compatible therefore desired…