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
Currently, -s will pipe the output directly to stdout, but I assume due to test concurrency the outputs are cached first and only shown after each test finishes, to avoid multiple outputs being jumbled. However, when the tests are run serially (with -n 1), they should be shown on screen immediately for faster monitoring and debugging.
Tagging @eirikurj who first brought up this point.
The text was updated successfully, but these errors were encountered:
Currently,
-s
will pipe the output directly to stdout, but I assume due to test concurrency the outputs are cached first and only shown after each test finishes, to avoid multiple outputs being jumbled. However, when the tests are run serially (with-n 1
), they should be shown on screen immediately for faster monitoring and debugging.Tagging @eirikurj who first brought up this point.
The text was updated successfully, but these errors were encountered: