Rain

Thanks for getting back! I'll also ask my Apple contact about the status.

#262 is one example of a performance issue on Mac.

Thanks for the questions! 1. At the moment tarpaulin hasn't been integrated with nextest yet -- see https://github.com/xd009642/tarpaulin/issues/992 for discussion. I believe nextest provides everything tarpaulin needs as machine-readable output,...

@nu11ptr good idea -- I've added a note to the homepage along with expanding the notes on the listing and running pages https://github.com/nextest-rs/nextest/commit/f4043b17a080533e52b94d6ae11743144318ed75

Yeah, that is the use case that I was thinking of. I agree that an all-or-nothing flag would be bad; the default will always be to run each test in...

This is going to require somewhat advanced concurrency-related and stability-related work so is not a good first issue, but I'll mark this as "help wanted" for now. If you'd like...

Been thinking about this -- I've figured out a way to do this on stable Rust using the `--logfile` option. We can rely on two things: 1. `cargo test` executes...

Update: nextest now sets a [`NEXTEST_RUN_ID` environment variable](https://nexte.st/book/env-vars.html#environment-variables-nextest-sets) which should help porting over some use cases to nextest. I don't plan to work on this for free. However: * If...

Thanks. This looks like an issue with a dynamic library provided by Rust, presumably created at build time, not being found at runtime. How is cargo installed? I'm guessing a...

OK, I know what's going on—we need to grab the value of "rustc --print sysroot" and set the sysroot path as part of LD_FALLBACK_LIBRARY_PATH properly. Will fix in the next...