On 6/26/20 11:37 PM, Jacob Bachmeyer wrote:
Pedro Alves wrote:
And again, people run the GDB testsuite in parallel mode, so your
assumption that the testsuite would stop immediately anyway doesn't
hold. One of the parallel runtest invocations bombs
out, while the others keep running, so by the time you get
back the prompt, other testcases already executed, and you don't
see the ERROR in the current terminal anymore.
This is a fundamental problem with slicing up the testsuite external to DejaGnu and
running multiple instances of runtest -- output that is supposed to be "last at the
end of the run" can be hidden away by other ongoing subset runs.
That's like arguing against parallelization, and saying that everyone
should run the testsuite in serial mode, and be OK with it taking 2 hours
instead of 30 mins to complete a run...
The parallel mode aggregates the summaries from the different runtest
invocations as a single summary at the end,
https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=contrib/dg-extract-results.py;h=30aa68771d491451f72d6dbd18f6d5ac339451b5;hb=HEAD
so I don't see what problem here is unsolvable. Again, the issue is that Tcl
ERRORs aren't tallied up on the DejaGnu summary, so the aggregated summary
doesn't contain those either.