Fix storing coverage data in cargo projects #3527
Merged
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 PR changes the condition we use to decide where to store the coverage data resulting from a coverage-enabled verification run. The previous condition would otherwise cause Kani to crash at the end of the run in some cases:
The PR also adds a new
cargo-coverage
mode tocompiletest
which runscargo kani
with the source-based coverage feature enabled. This ensures that coverage-enabledcargo kani
runs are also being tested, and will also be helpful for testing the upcoming coverage tool (#3121) with cargo packages.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.