Rain

Interesting, hadn't thought of it that way! Will think through the implications of that. I think that passed is _generally_ more important than skipped, but skipped + failed makes a...

If you run just one test on the CLI, though, you don't want to see the entire list of other tests as skipped. But I definitely see the argument for...

Thanks for the bug report! That's really interesting that `cargo test` doesn't download them. Sadly, nextest needs access to `cargo metadata`, which does download them -- though I wonder if...

Interesting, in my tests it does seem to work! ``` % rm -rf /opt/cargo/registry/cache/index.crates.io-6f17d22bba15001f/ % cargo metadata --filter-platform x86_64-pc-windows-msvc > /dev/null ... Downloaded 281 crates (26.8 MB) in 0.29s (largest...

Oh -- you're referring to _nextest_'s `platform-filter`. No, in this case it's actually nextest calling cargo-metadata internally that's at issue here.

Hi @hobovsky -- thanks for the report! It does look like that is the case at the moment. We can definitely do better here. I think this is because libtest...

Ah interesting, yeah -- _if_ tests are being run serially we can produce lines ASAP.

Hi, and thanks for the report. The saved metadata doesn't explicitly include the cargo profile, but it does implicitly have that information because a run from a saved archive file...

Hi there -- thanks for your interest! The reasons nextest requires source code while running builds are that: * sometimes, tests access files in the repo (e.g. test fixtures) *...

BTW if you have an external issue tracker I'd definitely be interested in subscribing to it!