-
Situation 1:
We embed cargo-llvm-cov into a docker image and use it as the base image for running CI. However, only invoked with `cargo llvm-cov`, the coverage is correct. If we instead build the bi…
-
### Describe the bug
Local build from a new repo fails with the following if the submodules havent been fetched:
```
llvm-cov-pretty> cargo build
Compiling llvm-cov-pretty v0.1.9 (/home/jayvdb/…
-
**Describe the bug**
We're using tarpaulin to collect coverage of end-to-end test of [kwctl](https://github.com/kubewarden/kwctl/), a Rust cli tool.
The tests are running fine and produce many `…
-
So found an interesting thing when developing cargo-tarpaulin and confirmed it exists also with cargo-llvm-cov and using the raw llvm tools. When `#[tracing::instrument]` is added to a function the fu…
-
In my workflow, this succeeds, and the expected results are uploaded into our deepsource tracker. (https://github.com/taiki-e/cargo-llvm-cov/issues/375 still happens; I'll see if I can dig up some det…
-
This tool already has `--exclude-from-report`, does it make sense to add black/white lists for toggling instrumentation on and off?
Like `--enable-coverage-for crate1 --enable-coverage-for crate2` or…
-
monitor_service will never be tested in this repository so including this in Codecov isn't reasonable.
-
UPDATE(taiki-e):
> If you want to ignore all `#[test]`-related code, consider using [coverage-helper](https://github.com/taiki-e/coverage-helper) crate version 0.2+.
>
> cargo-llvm-cov excludes c…
-
I tried this code (using [`thiserror`](https://github.com/dtolnay/thiserror/) v1.0.58):
```rust
use thiserror::Error;
#[derive(Error, Debug)]
pub enum E {
#[error("{}", if *.0 { "a" } els…
-
# bug
`llvm-cov` `warning: 1 functions have mismatched data` caused by comment line
## background
Found `llvm-cov` `warning: N functions have mismatched data`.
After debug, very suprisingl…