rapid-exabyte-76685
05/17/2022, 6:22 AM--test-output=all
is still only giving me the stdout from the test that fails… is there something that I could be doing wrong here? Also is it true that both --test-output=all
and --output=all
do the same thing?--test-output=all
from the successful tests, but on the failed test I see captured stdout setup
`captured stdout call`and `captured stdout teardown`and I’d really like to see this for the successful tests as well (in order to diagnose a race condition that is dependent upon the order in which tests are runcurved-television-6568
05/17/2022, 6:36 AMAlso is it true that bothYes, when provided after theand--test-output=all
do the same thing?--output=all
test
goal on the command line, it is.bitter-ability-32190
05/17/2022, 7:51 AMrhythmic-morning-87313
05/17/2022, 8:59 AM-- -s
?hundreds-father-404
05/17/2022, 12:37 PMrapid-exabyte-76685
05/17/2022, 1:40 PM./pants --process-execution-local-parallelism=1 test --force path/to/tests:integration_tests -- -m "integration"
-s
doesn’t seem to help… if I happen to get a run where all my tests pass I’m not seeing anything other than…
hh:mm:ss.sss [INFO] Completed: Run pytest - path/to/test/test_file_a.py:integration_tests succeeded.
<etc etc etc>
✓ path/to/test/test_file_a.py:integration_tests succeeded in x.yys.
print(f"The value is {value}")
statements to try and get some further insight on what order things are happening in but no output is appearing.hundreds-father-404
05/17/2022, 1:44 PM./pants test --debug path/to/tests:integration_tests -- -m integration
, what happens? That runs tests sequentially and in the foreground rather than background, so you see all outputrapid-exabyte-76685
05/17/2022, 1:47 PM-s
at the end helps 👍hundreds-father-404
05/17/2022, 1:49 PMAnd seems to consistently run the test modules in alphabetical order perhaps?That, I have zero idea. That's Pytest behavior outside of Pants's purview
rapid-exabyte-76685
05/17/2022, 1:51 PMhundreds-father-404
05/17/2022, 1:52 PM