Taiki Endo

> https://github.com/taiki-e/cargo-llvm-cov/pull/269/files#diff-b2812f19576dd53d0c35b107a322f58a00fce6977f4b5976e1961853982af3ccR357-R362 Flags not caught in those lines are [also passed to nextest](https://github.com/taiki-e/cargo-llvm-cov/blob/b72de10001e04ecad1530a32d221e7b828e8bfab/src/cli.rs#L447-L467); what is specified in the nextest profile does not affect the behavior of the cargo-llvm-cov itself, so...

Oh, do nextest seem to change the directory to which build artifacts are written? If so, surely the current cargo-llvm-cov cannot handle that.

> `-P ci` option (which I assume would pass, but not `--profile` Hmm, assuming nextest handles both the same way, if `-P ci` works, then `--profile ci` should also work....

> by default it writes to target/ If the (non-default) Nextest profile (not the Cargo profile) is set, will it still be written to `target/`? or subdirectory of `target/`? If...

It does not seem to be the directory to which cargo build artifacts are written when the --target-dir option is passed. `cargo llvm-cov nextest --text --profile ci` runs without problems...

> Does it mean that `llvm-cov` puts all the relevant artifacts to `target/llvm-cov-target`? Changing rustflags triggers rebuild of the entire dependencies, so the default is `target/llvm-cov-target` not `target`. However, show-env...

As for `--partition`, could you open another issue? And if possible, please provide a reproducible example that we can confirm `cargo nextest` works and `cargo llvm-cov nextest` doesn't. It helps...

Thanks. The problem here appears to be similar to #303, and perhaps something in the implementation of #31 is not working well.

`--exclude-from-report crate-a` can probably be used as a workaround, but has similar scalability issue as `--ignore-filename-regex` approach.

See https://github.com/taiki-e/install-action/issues/556 for the previous discussion.