Issues with running multiple tinderbuilds in parallel

[Joe Marcus Clarke]

On Fri, 2008-01-25 at 12:54 -0800, Ade Lovett wrote:
> Wanting to fully utilize my SMP tinderbox (8.0-CURRENT), I decided to  
> fire off a couple of tinderbuild's in parallel.
> 
> I'm getting some occasional really strange results with false-positive  
> leftovers, for example:
> 
> http://tinderbox.lovett.com/logs/5-i386/autoconf-2.61_2.log
> 
> or, for a little less extreme example:
> 
> http://tinderbox.lovett.com/logs/6-i386/gnome-desktop-2.20.3.log

How were you doing these builds?  That is, what Builds were running
simultaneously?  The fact that proc entries show up is very strange
since mtree is called with the -x argument which should prevent
descending into other mount points.

The extreme log looks as though the pristine mtree file was deleted, or
never properly generated.  This file should be generated into /tmp
inside the Build.  Is this /tmp directory mounted from a shared source?

> 
> 
> This is using nullfs, with only the distfiles being from a NFS-mounted  
> location.  Using NFS actually causes the machine to pretty  
> consistently lock up with NFS server not responding and processes  
> going unkillable, resulting in having to powercycle the machine.

Yeah, I saw this, too.  I used to do parallel builds on my i386 machine,
but recent GNOME versions really taxed this guy, so I dropped back to
one at a time.

Joe

-- 
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://marcuscom.com/pipermail/tinderbox-list/attachments/20080203/dbb1b70a/attachment.bin