lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler" <>
Subject RE: [JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.7.0_51) - Build # 9828 - Failure!
Date Tue, 25 Mar 2014 08:36:18 GMT

I also analyzed this specific events file. The events file looks quite fine, no endless logging
in this case. It was also only 95 MB (quite normal). So it looks like something else filled
the disk space, so checking size of event file is not really useful (only for the last case).
After reverting the virtual box to the clean snapshot it had 9 GB free. So something must
fill the disk (e.g. indexes other data). If this happens again, I will do a complete analysis
of whet is there to find in workspace. I only know, that all the 9 GB of space are inside
the Jenkins Workspace folder, so nothing outside fills the disk (like windows itsself).

I will think about it a bit more.

Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen

> -----Original Message-----
> From: [] On Behalf
> Of Dawid Weiss
> Sent: Tuesday, March 25, 2014 9:25 AM
> To:
> Cc: Mark Miller
> Subject: Re: [JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.7.0_51) - Build #
> 9828 - Failure!
> > Would it be possible to catch those cases while running tests (maybe
> > before the disk is full) and fail the build? Maybe something that the
> > event file is not allowed to grow beyond a specific size. If it grows,
> > the test framework fails the whole build? We can have something like
> > maximum size of 1 GB (configureable).
> I honestly think this is trying to cater for an insane specific scenario of a faulty
> test. Think of it: a single test that logs gigs to disk... Guarding against it may be
> next to impossible at the test framework level. We can put a condition in ant
> that checks for remaining temp space and fails if it's less than 5gb...
> Dawid
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: For additional
> commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message