jupyterhub / the-littlest-jupyterhub

Simple JupyterHub distribution for 1-100 users on a single server
https://tljh.jupyter.org
BSD 3-Clause "New" or "Revised" License
1.02k stars 338 forks source link

Test logs from tests extremely hard to read #899

Closed consideRatio closed 1 year ago

consideRatio commented 1 year ago

Typically I expect running tests to just show what test is being run, and then when the tests have been run, to see captured output associated with a failure if there is a failure.

With our test setup though, we get output streamed and everything becomes garbled. For example I know I'm not the only one to have been confused about seeing an error about not starting as PID 1 - but that was just a test that verified that we error nicely when starting as something else than PID 1 etc.

Here is another example where two tests pass run and we see the logs from that streamed. The first test is running something expected to fail - which it does (XFAIL), and one that is expected to succeed - which it does (PASSED). Skimming through this, one would think something is wrong - but its not, so its just a distraction.

image

I expected this to look more like this:

image

Suggested action