-
First, thanks for the great project, I've been using it for months without any issue =]
That said, I've been having trouble updating after commit 1fd2dc01ee34817858261bebae6a79cb9debc1f9 because `z…
-
Hello,
I'm currently using cargo-llvm-cov on Gitlab CI. Gitlab CI has a neat feature where it can display the coverage percentage right next to a change if it can parse it from the CI log via Regex…
-
Stack trace of where it gets stuck:
```
ALARM: working on the last Unit for 5 seconds
and the timeout value is 5 (use -timeout=N to change)
==3206839== ERROR: libFuzzer: timeout after 5 s…
-
PyO3 has a feature (`--multiple-pymethods`) which alters several code paths (such as inside a proc macro crate, the feature causes different generated code to be emitted).
Ideally I'd like to measu…
-
Currently, the trybuild crate does not contribute anything to the coverage report. I'm not sure whether this should be fixed in cargo-llvm-cov or trybuild. compiletest_rs, on the other hand, _does_ co…
-
I've just moved our projects from Tarpaulin to cargo-llvm-cov and coverage is much more accurate. I noticed however that our caching stopped working and it took me a good while to figure out why, but …
-
Hello,
Linking [regex](https://docs.rs/regex/1.5.4/regex/) crate on `x86_64-pc-windows-msvc` fails when using `-Z instrument-coverage`.
The link succeeds when using `-Z instrument-coverage=except-…
-
When running locally or on CI, I receive repeated error messages for each of my profraw files:
```
Error: 3 [ERROR] Error while executing llvm tools: Failure while running "/usr/share/rust/.rustup…
ecton updated
3 years ago
-
Current status: https://github.com/taiki-e/cargo-llvm-cov/issues/1#issuecomment-855210584
-
Ran this repo with the current Rust nightly toolchain.
The report shows zero coverage.