cargo-llvm-cov

Improve --show-missing-lines for multiple functions in a single line. (#183, thanks @vmiklos)

Limit the number of test threads to work around rust-lang/rust#91092. (#184)

Fix handling of RUSTC_WRAPPER, RUSTC, and similar environment variables and configs. (#180)

Distribute prebuilt binaries for aarch64 macOS. (#179)

Add --fail-uncovered-{lines,regions,functions} options to set the exit code based on uncovered {lines,regions,functions}. (#173)

Add --ignore-run-fail option to generate coverage even if tests fail. (#174)

cargo-llvm-cov no longer changes the current directory when running cargo. (#161)

Exclude build script from report by default. (#163)
You can use --include-build-script flag to include build script in report.

Set cfg(coverage_nightly) when nightly compiler is used. (#164)

Support short flags of --release (-r) and --features (-F). (#165)

Support custom profiles. (#166)

cargo-llvm-cov now always select the current toolchain. (#148)

Previously, if -C instrument-coverage is not available in the current toolchain, the nightly toolchain was used. (See release note of 0.2.0 for more information on the previous behavior.)

Make --remap-path-prefix optional. (#141)

Previously this flag was always used, but due to some bugs discovered we decided to disable it by default. If you were dependent on the behavior provided by this flag, you can use the same behavior by passing the --remap-path-prefix flag to cargo-llvm-cov.

Stabilize a few unstable options.

Update to stabilized -C instrument-coverage. (#130)

Support for -Z instrument-coverage in the old nightly will also be kept for compatibility.

Compatibility Note: In 0.2, if -C instrument-coverage or -Z instrument-coverage is not available in the default toolchain, running cargo llvm-cov will find and use nightly (this is almost the same behavior as 0.1). This behavior is necessary because only the recent nightly currently supports -C instrument-coverage (and also for compatibility with 0.1). This behavior will be changed in 0.3 to always select the default toolchain. If you are likely to be affected by the change in 0.3, cargo-llvm-cov will emit a warning. 0.3 is planned to be released after -C instrument-coverage is available in the stable toolchain.

Remove support of multiple values in --package and --exclude. (#133)

This behavior was unintentionally enabled in the older version of 0.1 and was deprecated in the recent version of 0.1.

Add --exclude-from-test option to exclude specific packages from the test but not from the report. (#131)

Add --exclude-from-report option to exclude specific packages from the report but not from the test. (#131)

Workspace members are now always included in the report unless specified by --exclude or --exclude-from-report. (#131)

Alleviate an issue where "File name or extension is too long" error occurs in Windows. (#126, thanks @aganders3)

Re-enable multiple values for --package and --exclude. (#127, thanks @aganders3)

This behavior was unintentionally enabled in older versions and disabled in recent versions.

We will support this again in 0.1.x for compatibility, but will remove it in 0.2.x.

Distribute prebuilt binaries for aarch64 Linux (gnu and musl).

Add show-env subcommand. (#115, thanks @davidhewitt)

cargo-llvm-cov no longer sets CARGO_TARGET_DIR. (#112, thanks @smoelius)

cargo-llvm-cov can now properly exclude arbitrary CARGO_HOME and RUSTUP_HOME from reports.