Runtime and instrumentation version mismatch about cargo-llvm-cov HOT 6 CLOSED

This is a rustc (or LLVM) bug that occurs when there is a dylib crate in dependencies on windows-msvc (rust-lang/rust#124372).

Workaround for your case is disabling the dynamic_linking feature of bevy.

from cargo-llvm-cov.

My first thought is that you specified a different LLVM version of llvm-profdata (#362) or linked a C binary built with another LLVM version with coverage-related compilation flags enabled, but given that 797582847 is clearly an unusual value, the problem may be somewhere else.

In any case, this issue needs a reproduction. It is always difficult to investigate an issue unless I can reproduce it on my end.

from cargo-llvm-cov.

So on my simpler project that previous had code coverage working, I added Bevy to it and now its not working. So there is probably some issue with those dependencies or its my system. If you do want to look into it more I uploaded the repo here: https://github.com/mdeering24/coverage_debugging

cargo llvm-cov --lcov --output-path ./coverage/lcov.info

Finished `test` profile [optimized + debuginfo] target(s) in 1.57s
     Running unittests src/main.rs (target\llvm-cov-target\debug\deps\code_coverage-fa9d433ff32f3e68.exe)

running 1 test
test test::test_double ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

LLVM Profile Error: Runtime and instrumentation version mismatch : expected 9, but get 867837439
    Finished report saved to ./coverage/lcov.info

from cargo-llvm-cov.

Thanks for the repro. I can reproduce this on the latest nightly on Windows, and I can't reproduce this on macOS, so I'm marking this as Windows-specific issue.

from cargo-llvm-cov.

Closing in favor of upstream bug report.

from cargo-llvm-cov.

Thanks for looking into this. I appreciate it

from cargo-llvm-cov.