-
Take a look at https://github.com/taiki-e/cargo-llvm-cov, hopefully will be less manual than what we're doing now!
Also look at https://github.com/taiki-e/coverage-helper, and see if we can run tests…
-
# 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…
-
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…
-
Code coverage is collected by [collect_coverage.rs](https://github.com/bazelbuild/rules_rust/blob/main/util/collect_coverage/collect_coverage.rs). This binary invokes `llvm_profdata` and `llvm_cov`, w…
-
#### Description
This issue occurs with numerous tests ran within a suite of 415 other tests. The vast majority of these tests are of the same complexity as the test shown below (i.e.: simple methods…
-
### Description of the bug:
Hello Everyone,
Starting with Bazel 7.2.1 it's no longer possible to generate c++ code coverage using a hermetic Clang toolchain. I am using pw_toolchain_bazel to g…
-
LLVM clang also understands the gcc options for enabling coverage collection (e.g. `--coverage` and `-fprofile-arcs -ftest-coverage`). But - in that compatibility mode - llvm targets a certain gcc/gco…
-
The text and the html report for my project https://github.com/jendrikw/clearurls show that one line in rules.rs is missing coverage, but I can't find it. I tried `--show-missing-lines`, but that did …
-
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 to fuzz our substrate runtime but getting error:
```
error: Failed to load coverage: 'target/x86_64-unknown-linux-gnu/coverage/x86_64-unknown-linux-gnu/release/main': Malformed coverage data…