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
All the tests are run with RUST_TEST_THREADS=1 to work around [https://github.com/rust-lang/rust/issues/91092]. You can pass --test-threads (e.g., --test-threads=$(nproc)) to override this behavior. (As for nextest, we also set NEXTEST_TEST_THREADS=1.)
But in nextest--test-threads seems to be ignored when NEXTEST_TEST_THREADS=1 is set. Could cargo-llvm-cov detect --test-threads being set and not set NEXTEST_TEST_THREADS=1 then?
The text was updated successfully, but these errors were encountered:
cargo llvm-cov nextest --test-threads=16 --no-clean --no-fail-fast
I'm still seeing only one test being executed at a time, runs for about an hour.
Edit: Actually, towards the end the number of tests running is going up, but stays around 1-2 during the start, strange.
FYI, since cargo-llvm-cov 0.5.20, we no longer set RUST_TEST_THREADS/NEXTEST_TEST_THREADS and now adopt a more efficient alternative to workaround rustc bug.
The README states:
But in
nextest
--test-threads
seems to be ignored whenNEXTEST_TEST_THREADS=1
is set. Could cargo-llvm-cov detect--test-threads
being set and not setNEXTEST_TEST_THREADS=1
then?The text was updated successfully, but these errors were encountered: