Michael Peters wrote:
Michael G Schwern wrote:
Michael Peters wrote:
make test || echo -e "\a"
I keep digging away at this because I'm looking for a problem other than "I
want to see the first failure". And that's what I'm hearing from you and from
Matisse and everyone else. Yours is a little different, it's "I want to be
alerted on first failure".
Not just that I want to be alerted. I want to be able to work and fix things. A
45 minute test suite is also going to be machine intensive (and in my case have
other services running that I'd need to stop/restart to be able to
troubleshoot). So having the whole test suite come to a stop is actually
important. Just knowing that a failure happened 3 minutes in isn't much help if
I don't get to immediately start working on the fix.
You see how this is distinct from "halt on first failure"? It gives me a lot
more room for different solutions that don't involve just cutting off all the
following information.
I can see why sometimes and (some people) want all the information and I don't
think you should remove that option. Just add the option to stop for those of us
who don't.
If we're concerned about losing the diagnostics, then just have it fail
on the NEXT test...
Put the...
if ( any failures ) { bail out }
... at the beginning of the ok call, not at the end.
Or give us the damned rope and allow us to make it bail, knowing we
don't give one hoot about the diagnosics.
If we really care, we can just run that single test again with verbose
on anyway.
Adam K
