Michael Peters wrote:
> Michael G Schwern wrote:
>
>> Ok, why do you want to stop it as fast as possible when a failure occurs?
>
> I have a 45 minute test suite and I want to work on the first failure as soon
> as
> possible. I also have multiple desktops and am doing other things in another
> desktop, so I want to know as soon as the failure happens so that I can start
> working on it:
>
> make test || echo -e "\a"
>
> Would be nice if that would beep after the first failure instead of after 45
> minutes and the whole thing is done.
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".
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.
--
Look at me talking when there's science to do.
When I look out there it makes me glad I'm not you.
I've experiments to be run.
There is research to be done
On the people who are still alive.
-- Jonathan Coulton, "Still Alive"
