whole jail contents in `leftovers'

[Alexey V. Degtyarev]

> > Actually, my tinderbox installation is quite old (CVS from Feb 02), and
> > I'll try to update it as well as it's chroot contents, but maybe the bug
> > is already known and it'll save me some efforts :)
> 
> This should be fixed in the latest version.  The problem occurs when a
> previous port build fails.  The fix was to completely refresh the Build
> if a failure is detected.  The result should be that the next port build
> starts with a clean Build environment.

 Do you mean the latest release version or CVS snapshot? 
 
 I have exactly the same issue on the 3.2 from ports almost every time
 while parallel in-memory builds and never while one-by-one builds. I'm
 using 7.1-RELEASE and nullfs mounts, the ports tree and build's mount
 points are mounted via memory disks to avoid the hard disks overload.
 If I run multiple instances of ./tc tinderbuild command in parallel -
 the problem occurs very often leaving some ports (randomly) having
 extremely large leftovers log. However I can't catch this trouble if I
 run a next tinderbuild only after the previous one done.

 How can I help you to debug the problem?

-- 
Alexey V. Degtyarev