Rain
Thanks for the report! This looks like it's part of https://github.com/nextest-rs/nextest/issues/325. Would you like to contribute a fix? The logic for cargo config parsing is in https://github.com/nextest-rs/nextest/blob/main/nextest-runner/src/cargo_config.rs. You just need...
This has landed, and will be part of the next release of nextest in the next 2-3 days.
Just released cargo-nextest 0.9.40 with support for this -- binaries will be available within the next 20 minutes.
Just did! Unfortunately each time you update I'll have to re-approve it. If you do another PR with a simple change (like the change to `set_env_vars` above) I can land...
Thanks! Just saw this, apparently I missed your last message. Sorry about that! > As far as I can tell, those invocations shouldn't pick up the environment variables defined in...
The macOS test is definitely flaky, I've been meaning to get to the bottom of it for a while. The Windows issues are pretty fun, I know what's going on....
I'm going to get this out in the next couple of days. Thanks again!
BTW I ended up redoing [the `EnvironmentMap` construction](https://github.com/nextest-rs/nextest/commit/3cde3d0b2f9403c83e1ac77ebde4b23edcfa43b4) to fix some lingering issues including case-insensitivity on Windows.
Thank you for the contribution! Unfortunately this isn't quite the right way to go about it: `run-help.txt` is generated from `cargo nextest run -h`, so the way to do this...
I'd recommend doing a rebase and force push rather than a merge.