lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dawid Weiss <dawid.we...@cs.put.poznan.pl>
Subject Re: [JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.7.0_51) - Build # 9828 - Failure!
Date Wed, 26 Mar 2014 07:59:07 GMT
The framework itself should clean up its own directories and files but I
don't think it removes test files. It definitely doesn't remove anything
in case of an unsuccessful build -- did those builds pass?

Dawid


On Wed, Mar 26, 2014 at 1:47 AM, Uwe Schindler <uwe@thetaphi.de> wrote:

> Hi,
>
>
>
> the windows VM again ran out of disk space a minute ago.
>
>
>
> The Windows VM had initially approx. 8 GB free space. After running both
> workspaces (4.x and trunk), the Solr-core work folder used approx. 3 to 4
> GiB each. Looking into the directory, it looks like (maybe that is a
> windows problem), nothing is cleaned up in the JUnit runner directory. I
> was expecting that tests clean up after running, which seems no longer be
> the case.
>
>
>
> Trunk:
>
>
>
>
>
>
>
> 4.x
>
>
>
>  -----
>
> Uwe Schindler
>
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
> http://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
>
>
> > -----Original Message-----
>
> > From: dawid.weiss@gmail.com [mailto:dawid.weiss@gmail.com] On Behalf
>
> > Of Dawid Weiss
>
> > Sent: Tuesday, March 25, 2014 9:47 AM
>
> > To: dev@lucene.apache.org
>
> > Subject: Re: [JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.7.0_51) -
> Build #
>
> > 9828 - Failure!
>
> >
>
> > These tests are loooong, so theoretically we could add a guard thread at
> the
>
> > suite level that would watch for disk capacity thresholds...
>
> > but it still seems like an overkill to me.
>
> >
>
> > Dawid
>
> >
>
> > On Tue, Mar 25, 2014 at 9:36 AM, Uwe Schindler <uwe@thetaphi.de> wrote:
>
> > > Hi,
>
> > >
>
> > > 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
>
> > > http://www.thetaphi.de
>
> > > eMail: uwe@thetaphi.de
>
> > >
>
> > >
>
> > >> -----Original Message-----
>
> > >> From: dawid.weiss@gmail.com [mailto:dawid.weiss@gmail.com<dawid.weiss@gmail.com>]
> On
>
> > Behalf
>
> > >> Of Dawid Weiss
>
> > >> Sent: Tuesday, March 25, 2014 9:25 AM
>
> > >> To: dev@lucene.apache.org
>
> > >> 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: dev-unsubscribe@lucene.apache.org For
>
> > >> additional commands, e-mail: dev-help@lucene.apache.org
>
> > >
>
> > >
>
> > > ---------------------------------------------------------------------
>
> > > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For
>
> > > additional commands, e-mail: dev-help@lucene.apache.org
>
> > >
>
> >
>
> > ---------------------------------------------------------------------
>
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional
>
> > commands, e-mail: dev-help@lucene.apache.org
>

Mime
View raw message