Rain
Nextest isn't a custom test harness (it's a custom test runner) so I don't think there's any upside or downside of supporting this for nextest.
Should I also change the github config to run on PRs?
Updated! Sorry about the delay, this looks good to go now (hopefully tests pass)
Maintainer of nextest here, happy to help if there are any issues! For Miri it was dead simple: https://github.com/rust-lang/miri/pull/2398 In particular, I noticed this bullet point at https://github.com/rustwasm/wasm-bindgen/blob/main/crates/test/README.md: > Running...
Hmmm, interesting. I've never tried it on single-crate projects, but I wonder if there's a way to make it work with some creativity. For example you could have an outer...
Hi -- The immediate problem you have is probably easiest to solve via test groups: https://nexte.st/book/test-groups For network isolation, I'm not completely opposed to it, and there are related issues...
Thanks for the response! > By default a merge commit is checked out. If you look at the SHA that is checked out, it doesn't match your local commit SHA....
Would there be any interest in revisiting this decision at all?
FWIW, since my earlier post I've reversed my opinion -- I've seen proprietary data which has led me to believe that checking out the merge commit, while not as pure...
It's not a problem per se, it's just that the data showed that using the merge conmit provided more relevant CI results.