Feature/question: Only show the verbose output of failed tests #13322
Assignees
Labels
Comments
|
After with emailing with @tristan957 privately I realized I can at least achieve my first 2 goals by using the combination of flags: |
|
For 3 & 4, can you go into detail about what you mean by hiding? |
|
Regarding 3, even with Regarding 4, if I use |
|
This is gonna require input from others to see if they are actionable. I would love to at least get rid of these backtraces though. |
bonzini
added
bug
test targets
exception
|
With 1 and 2 fixed, let's focus on the |
|
@bonzini maybe we should create a new issue for that? |
|
Yes, if you have a reproducer. |
|
I do not. |
|
It's python/cpython#114177, and it's at least partly mitigated by python/cpython#111983 which was documented as Issue warning message instead of having :class:`RuntimeError` be displayed when
event loop has already been closed at :meth:`StreamWriter.__del__`.So I think the remaining bit is "do not print logs of interrupted jobs if the interruption was caused by --maxfail=1". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm having the problem that none of the different verbosity flags of meson (that I can find) do the thing that I would like to happen:
I want to show the output of failed tests, but not clutter my screen with any output of passed or skipped tests.
What I want (from important to less important)
--maxfailMaybe I just don't know the correct options, but with the ones I know I can get the following all suboptimal behaviours
To reproduce in the postgres repo set up like this:
--quietshows this: short but impossible to debug at all, still shows skipped tests thoughNo flag shows this: more clutter still impossible to debug
--verboseshows this: maximum clutter, but at least it shows what failed (both randomly in the middle and all the way at the end)too large for github issue description so as attachment: verbose-output.txt
output to large so as attachment:
verbose-output.txt
--verbose --maxfail=1gives me this: early failure, which is nice but still quite cluttered with passing tests and now I have to scroll up quite a bit through clutter caused by interupted tests before I find the real failureoutput to large so as attachment:
verbose-maxfail.txt
The text was updated successfully, but these errors were encountered: