Re: [RFA] bailing out of tests with multiple errors or timeouts

[Joel Brobecker <brobecker@adacore.com>]

There was a discussion in the past about this, and we thought that
the benefit of continuing after detecting a TIMEOUT was, overall,
usually nul. A timeout is often a source of loss of synchronization
between what you're sending and the associated output, so continuing
in that situation isn't going to be all that useful. I'm sure we'll
find some counter examples, but the ration between benefits vs time
wasted is probably going to remain very small.

So the conclusion the two of us who discussed this reached was that
we should just abort the testcase at the first TIMEOUT.  But rather
than do it in an ad hoc way as is done here, do it systematically.
The problem is, I haven't found a way to do this, yet. I thought
about raising an exception, but I don't think there is a way for
the testsuite to trap it before dejagnu sees it...

-- 
Joel