findepi commented on PR #13045: URL: https://github.com/apache/datafusion/pull/13045#issuecomment-2438666471
`cargo test` vs `cargo nextest` -- there is more to than just speed. `cargo nextest` runs each test in separate process, providing awesome isolation. Is it good for developers? it should, but it actually depends. The tools i tried (RustRover, VS Code) are capable of running a test module, but they don't seem to understand nextest, so they run **without** process-per-test isolation, which kills productivity if tests actuall leverage isolation. (@alamb do you or someone at influx have a solution to this?) so - if it's just supported but not guaranteed (this PR), i am fine with the change -- LGTM - if we want to embrace nextest as _the way_ to run tests -- i am probably fine to, but let's make sure we understand benefits and drawbacks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
