Add support for generating coverage #296
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds experimental support for generating coverage using LLVM and
cargo-llvm-cov
. Note that replacingcargo-llvm-cov
would be simple. It might simplify stuff even ascargo-llvm-cov
basically just invokesllvm-profdata
andllvm-cov
.How to use
Suppose you have a setup like in the
examples
directory of the repository. Then:cargo install cargo-llvm-cov
rustup toolchain install nightly --component llvm-tools-preview
cargo test
cargo-test-fuzz test-fuzz target --no-instrumentation --replay corpus --coverage
Coverage is generated as HTML in
target/llvm-cov/html
.TODO:
llvm-tools-preview
andcargo-llvm-cov
get installed or promt for installation.warning: 4 functions have mismatched data
I suspect this is due to the fact that test-fuzz injects code into the function-to-test here:
test-fuzz/macro/src/lib.rs
Line 727 in c247ff5
Either move that code somewhere else, or put it into a function, ad a
no_coverage
instruction and call that from the target function.Details
The follwing commands are executes to generate coverage. We should validate them:
fixes #293