Add --no-clean flag #214
Merged
Add --no-clean flag #214
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
bors r+ |
|
Build succeeded: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
cargo-llvm-cov cleans some build artifacts by default to avoid false positives/false negatives due to old build artifacts.
This behavior is disabled when
--no-clean,--no-report, or--no-runis passed, and old build artifacts are retained.When using these flags, it is recommended to first run
cargo llvm-cov clean --workspaceto remove artifacts that may affect the coverage results.cargo llvm-cov clean --workspace # remove artifacts that may affect the coverage results cargo llvm-cov --no-cleanCloses #198 (In the long term I want to remove the need for these clean, but it is not easy.)