Re: make -j and errors

2012-09-26 Thread Ted Unangst
On Thu, Sep 27, 2012 at 00:05, Marc Espie wrote: > You probably don't see the difference, because you run short stuff with > not enough jobs. But for long running stuff, you will sometimes have an > error, and notice it only a few minutes afterwards, 5000 lines of scrollback > later, when they oth

Re: make -j and errors

2012-09-26 Thread Marc Espie
On Wed, Sep 26, 2012 at 12:41:10PM -0700, Philip Guenther wrote: > On Wed, Sep 26, 2012 at 12:01 PM, Ted Unangst wrote: > > I don't see what we gain by killing jobs. If the scheduler dice had > > come down differently, maybe those jobs would finish. > > > > Here's a downside, albeit maybe a stret

Re: make -j and errors

2012-09-26 Thread Philip Guenther
On Wed, Sep 26, 2012 at 12:01 PM, Ted Unangst wrote: > I don't see what we gain by killing jobs. If the scheduler dice had > come down differently, maybe those jobs would finish. > > Here's a downside, albeit maybe a stretch. What if the job doesn't > like being killed? You're changing behavior

Re: make -j and errors

2012-09-26 Thread Ted Unangst
On Wed, Sep 26, 2012 at 18:21, Marc Espie wrote: > I've been thinking some more about it. > > POSIX says very little about parallel makes. > > The more I think about it, the more I think gnu-make's approach on this is > stupid: if a job errors out in a fatal way, what do we gain if we keep > goin

Re: make -j and errors

2012-09-26 Thread Darrin Chandler
On Wed, Sep 26, 2012 at 06:21:34PM +0200, Marc Espie wrote: > "but what about commands that take a long time to run ?" > Well, make already has a standard mechanism to flag those, that's called > .PRECIOUS What if most everything takes a fairly long time to run? Say, largish C++ sources or whateve

Re: make -j and errors

2012-09-26 Thread Kenneth R Westerback
On Wed, Sep 26, 2012 at 06:21:34PM +0200, Marc Espie wrote: > I've been thinking some more about it. > > POSIX says very little about parallel makes. > > The more I think about it, the more I think gnu-make's approach on this is > stupid: if a job errors out in a fatal way, what do we gain if we

make -j and errors

2012-09-26 Thread Marc Espie
I've been thinking some more about it. POSIX says very little about parallel makes. The more I think about it, the more I think gnu-make's approach on this is stupid: if a job errors out in a fatal way, what do we gain if we keep going ? Especially for high -j values, the quicker we die, the bet