-
I used grcov to measure the test coverage of the project, but the results didn't seem very good, both source-based and gcov-based.@richkadel
The source-based approach is shown here.
To test th…
-
Hi,
When using this project inside the official [rust docker image](https://hub.docker.com/_/rust), the coverage report include stuff from `/usr/local/cargo/registry/src/`.
I'm not sure how to …
-
Between nightly versions 2022-01-14 and 2022-01-15, [grcov](https://github.com/mozilla/grcov) 0.8.2 lost track of 82% of the coverage of [BonsaiDb](https://github.com/khonsulabs/bonsaidb) when using t…
ecton updated
2 years ago
-
I am trying to create an enclave where the “inner” part (basically containing the business logic) is instrumented with LLVM's SanitizerCoverage, but having some problems due to Cargo's building of the…
-
We already support test coverage for binary crate (https://github.com/taiki-e/cargo-llvm-cov/issues/1#issuecomment-857738242), but it would be nice if we could support another way as well.
Somethin…
-
with llvm-cov there are BRF entries which the tool does not understand
Reproducable on lz4_flex https://github.com/PSeitz/lz4_flex
```
cargo llvm-cov --workspace --lcov --output-path lcov1.info
…
-
It would be useful to have a flag to remove only artifacts that may affect the coverage results, using the same way as https://github.com/taiki-e/cargo-llvm-cov/pull/79.
```
cargo llvm-cov clean -…
-
Would you consider a PR to pass a `-failure-mode` option to `llvm-profdata merge`?
https://llvm.org/docs/CommandGuide/llvm-profdata.html#cmdoption-llvm-profdata-merge-failure-mode
-
Include base and --all-features for build, test, and clippy
-
The current way does not handle it correctly when the version is specified in a cargo or rustup specific way (e.g., `cargo +nightly-...`, `rustup run +nightly-...`).
https://github.com/taiki-e/ca…