You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our test suite is kinda hacky because we really want to test with specific environment variables set, but we cannot easily set those because Cargo tests are run in parallel in different threads.
Previous I only consider cargo-nextest if performance matters, I forgot that its process model would help isolate tests and would be especially useful for us because our tests sets environment variables
Previous I only consider cargo-nextest if performance matters, I forgot that its process model would help isolate tests and would be especially useful for us because our tests sets environment variables
Our test suite is kinda hacky because we really want to test with specific environment variables set, but we cannot easily set those because Cargo tests are run in parallel in different threads.
Using
cargo-nextest
to run our test suite would solve that issue, since it runs each#[test]
in it's own process (but still in parallel), and thus setting an environment variable would not affect other test runs. See also rust-lang/rust#47506 and rust-lang/rust#67650.WDYT @NobodyXu?
The text was updated successfully, but these errors were encountered: