Rain
(Like most Rust devtools, nextest is a full-fledged Windows application. There is no attempt to emulate Unix on Windows -- many of the same types are used, but with `#[cfg(unix)]`...
Oh no, I was wrong. In reality, on receiving Ctrl-C, nextest doesn't do anything at all. It just lets tests exit by themselves. See: https://github.com/nextest-rs/nextest/blob/208d6e527098cf347f731975f3606249ee1cc791/nextest-runner/src/runner/windows.rs#L86-L90 I actually think this might...
> Even though I don't know why exactly it happens, I don't think a systemic issue should be patched up on the side of the tests. Ah I meant just...
Thanks @tgross35 -- will follow up when we next have time.
Yeah, a test attempting to exercise both paths sounds good. I'll work on that once #131823 lands. > Hm. I guess one can write internal unit-tests where the APIs are...
All right, rebased and added a test to exercise both paths.
@rustbot review
Thanks for the quick response! Yes, I'm suggesting removing those impls. It'll be a breaking change, but I think one that's good from an API misuse perspective. How about just...
With apologies, I need to tackle something urgently at work this week. Hoping to look at this by the end of the week.
Thank you! Could you tell me what config you wanted to set at the user level?