[Omake] Stopping *immediately* on errors

[Jason Hickey]

Benjamin Pierce wrote:
> Since Aleksey pointed it out last week, I've been happily running  with 
> '-j 10' and soaking up all the cycles on my dual-processor  machines.  
> The one time when this is not so great is when one of the  sub-processes 
> encounters an error, since the message that gets  printed tends to get 
> completely buried in the rest of the output from  the others.  (I do get 
> told at the end that *something* failed, but  then I have to grub around 
> quite a bit to find it.)
> 
> It would be nice if there were a flag something like the opposite of - k 
> (or perhaps this should even be the default behavior?), that would  
> immediately kill off all other subprocesses -- or at least prevent  them 
> from producing any more output -- as soon as one has failed.   Would 
> this be hard?

Aleksey has suggested an alternate behavior, where when an error occurs 
that output is reprinted at the end (in non-interleaved form).  Would 
this be preferable instead-of/in-addition-to the -[no]k option?

Jason

-- 
Jason Hickey                  http://www.cs.caltech.edu/~jyh
Caltech Computer Science      Tel: 626-395-6568 FAX: 626-792-4257