cargo-llvm-cov-report Generate coverage report USAGE: cargo llvm-cov report [OPTIONS] OPTIONS: --json Export coverage data in "json" format If --output-path is not specified, the report will be printed to stdout. This internally calls `llvm-cov export -format=text`. See for more. --lcov Export coverage data in "lcov" format If --output-path is not specified, the report will be printed to stdout. This internally calls `llvm-cov export -format=lcov`. See for more. --cobertura Export coverage data in "cobertura" XML format If --output-path is not specified, the report will be printed to stdout. This internally calls `llvm-cov export -format=lcov` and then converts to cobertura.xml. See for more. --codecov Export coverage data in "Codecov Custom Coverage" format If --output-path is not specified, the report will be printed to stdout. This internally calls `llvm-cov export -format=json` and then converts to codecov.json. See for more. --text Generate coverage report in “text” format If --output-path or --output-dir is not specified, the report will be printed to stdout. This internally calls `llvm-cov show -format=text`. See for more. --html Generate coverage report in "html" format If --output-dir is not specified, the report will be generated in `target/llvm-cov/html` directory. This internally calls `llvm-cov show -format=html`. See for more. --open Generate coverage reports in "html" format and open them in a browser after the operation. See --html for more. --summary-only Export only summary information for each file in the coverage data This flag can only be used together with --json, --lcov, or --cobertura. --output-path Specify a file to write coverage data into. This flag can only be used together with --json, --lcov, --cobertura, or --text. See --output-dir for --html and --open. --output-dir Specify a directory to write coverage report into (default to `target/llvm-cov`). This flag can only be used together with --text, --html, or --open. See also --output-path. --nextest-archive-file Path to nextest archive --failure-mode Fail if `any` or `all` profiles cannot be merged (default to `any`) --ignore-filename-regex Skip source code files with file paths that match the given regular expression --show-instantiations Show instantiations in report --fail-under-functions Exit with a status of 1 if the total function coverage is less than MIN percent --fail-under-lines Exit with a status of 1 if the total line coverage is less than MIN percent --fail-under-regions Exit with a status of 1 if the total region coverage is less than MIN percent --fail-uncovered-lines Exit with a status of 1 if the uncovered lines are greater than MAX --fail-uncovered-regions Exit with a status of 1 if the uncovered regions are greater than MAX --fail-uncovered-functions Exit with a status of 1 if the uncovered functions are greater than MAX --show-missing-lines Show lines with no coverage --include-build-script Include build script in coverage report --dep-coverage Show coverage of the specified dependency instead of the crates in the current workspace. (unstable) --skip-functions Skip exporting per-function coverage data. This flag can only be used together with --json, --lcov, or --cobertura. --doctests Including doc tests (unstable) This flag is unstable. See for more. -q, --quiet Display one character per test instead of one line -p, --package Package to run tests for -j, --jobs Number of parallel jobs, defaults to # of CPUs -r, --release Build artifacts in release mode, with optimizations --profile Build artifacts with the specified profile -F, --features Space or comma separated list of features to activate --all-features Activate all available features --no-default-features Do not activate the `default` feature --target Build for the target triple When this option is used, coverage for proc-macro and build script will not be displayed because cargo does not pass RUSTFLAGS to them. --coverage-target-only Activate coverage reporting only for the target triple Activate coverage reporting only for the target triple specified via `--target`. This is important, if the project uses multiple targets via the cargo bindeps feature, and not all targets can use `instrument-coverage`, e.g. a microkernel, or an embedded binary. -v, --verbose Use verbose output Use -vv (-vvv) to propagate verbosity to cargo. --color Coloring: auto, always, never --remap-path-prefix Use --remap-path-prefix for workspace root Note that this does not fully compatible with doctest. --include-ffi Include coverage of C/C++ code linked to Rust library/binary Note that `CC`/`CXX`/`LLVM_COV`/`LLVM_PROFDATA` environment variables must be set to Clang/LLVM compatible with the LLVM version used in rustc. --manifest-path Path to Cargo.toml --frozen Require Cargo.lock and cache are up to date --locked Require Cargo.lock is up to date --offline Run without accessing the network -Z Unstable (nightly-only) flags to Cargo, see 'cargo -Z help' for details -h, --help Print help information