cargo-llvm-cov: When used with nextest, `--profile ` is not being processed correctly

cc https://github.com/taiki-e/cargo-llvm-cov/issues/120

I’m running

NEXTEST_PROFILE="scripts/ci/gitlab/nextest.toml"
cargo llvm-cov nextest run
        --workspace
        --profile testnet
        --verbose
        --locked
        --features=runtime-benchmarks,runtime-metrics
        --no-fail-fast
        --color always
        --verbose
        --include-build-script
        --html
        --output-dir $ARCHIVE

And getting an error:

Running `CARGO_INCREMENTAL=0 CARGO_LLVM_COV=1 LLVM_PROFILE_FILE='/builds/TriplEight/target/llvm-cov-target/test-%p-%m.profraw' NEXTEST_TEST_THREADS=1 RUSTFLAGS='-Cdebug-assertions=y -Dwarnings -C instrument-coverage --cfg=coverage --cfg=trybuild_no_target' RUST_TEST_THREADS=1 /usr/local/rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/cargo nextest run --manifest-path /builds/TriplEight/Cargo.toml --target-dir /builds/TriplEight/target/llvm-cov-target run --workspace --profile testnet --locked --features=runtime-benchmarks,runtime-metrics --no-fail-fast --color always -v`
error: profile `scripts/ci/gitlab/nextest.toml not found (known profiles: default, default-miri)`

Ran with --cargo-profile, like in nextest doc, with the exactly the same result. Same when I removed run after nextest.

Is there any workaround for it by now?

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 15 (8 by maintainers)

Most upvoted comments

Closing as it has been confirmed that passing the correct option (–config-file) works.

Hmm, this is odd because we already ignore --profile option on nextest.

Could you check does https://github.com/taiki-e/cargo-llvm-cov/commit/ebd846b97608ee8a8c5c5a31216f8f78bd5b0f9c (in nextest-profile branch) fixes this?

(Also please remove run after cargo llvm-cov nextest.)