On 04/26/07 10:25, Darren J Moffat wrote: > Danek Duvall wrote: >> On Wed, Apr 25, 2007 at 08:33:36AM +0200, Roland Mainz wrote: >> >>> (you're using dmake which means that an error long before this point may >>> cause this build failure (and dmake just unrolls all the output of the >>> pending jobs)) ? >> >> Useful tip: put DMAKE_OUTPUT_MODE=TXT2 in your environment, and dmake >> will >> spit out the build output serially. This means that there will be long >> gaps between spurts of output into the log, but it makes the resulting >> log >> much more readable. > > Doesn't sound like this would have any impact on the actual build time > so any reason why nightly shouldn't make this the default ?
It could also speed up highly parallel builds over nfs. I have noticed considerable contention on the home-grown nfs rwlock for the nightly.log file when building with aggressive max jobs (like 64-128); at one stage I changed some nightly environment variable that influenced the log to accumulate in /tmp - it's copied to the log dir at the end, anyway. Gavin
