Hi Robert,

Thanks for pointing to that issue. Indeed the leftover test files in Lucene 
take approx. 3 GB per build. With our 9 builds that’s 30 GB - useless. If the 
tests clean up the thing successfully after running, we should be fine.

If you are not able to solve this in near feature I would add the following 
command at the end of our shell script that runs the builds:
        find $WORKSPACE/checkout/lucene/build/test/ -type d -depth 1 | xargs rm 
-rf 
This would preserve test result files but delete all directories inside.

Alternatively maybe the test task should do this after running tests?

As noted before, running "ant clean" at the end of build process is not working 
as Jenkins need to collect test results.

Uwe

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de


> -----Original Message-----
> From: Robert Muir [mailto:rcm...@gmail.com]
> Sent: Friday, April 22, 2011 2:31 PM
> To: dev@lucene.apache.org
> Subject: Re: Lucene Jenkins slave out of disk
> 
> On Thu, Apr 21, 2011 at 3:42 AM, Uwe Schindler <u...@thetaphi.de> wrote:
> > OK,
> >
> > I was not aware that you took action, too. Because there is the
> > message about Jenkins shutdown, I was assuming that you are fixing the
> master.
> >
> > About the Lucene slave, the problem we have is: Our tests need lots of
> > disk space for large indexes.
> 
> and this is a known bug in our build that should really be fixed:
> https://issues.apache.org/jira/browse/LUCENE-2796
> 
> i'll try to work on this today.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional
> commands, e-mail: dev-h...@lucene.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to