lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LUCENE-4301) re-enable test timeout, but factor in nightly, multiplier, clover
Date Mon, 13 Aug 2012 11:51:37 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433078#comment-13433078
] 

Uwe Schindler edited comment on LUCENE-4301 at 8/13/12 10:50 PM:
-----------------------------------------------------------------

The problem with this test its that it must create an index with > 2 billion terms...

With some similar problems regarding overflow of document numbers, I used a trick in another
test:

{code}
IndexReader small = ...
IndexReader[] arr1 = new IndexReader[count];
Arrays.fill(arr1, small);
MultiReader intermediate = new MultiReader(arr1);
IndexReader[] arr2 = new IndexReader[count];
Arrays.fill(arr2, intermediate);
MultiReader huge = new MultiReader(arr2);
{code}

Producing a composite reader with count * count * small.maxDoc() docs, but spending almost
no RAM. Maybe we can do something similar here (wrapping this huge synthetic reader with SlowMultiReaderWrapper)?

                
      was (Author: thetaphi):
    The problem with this test its that it must create an index with > 2 billion terms...

With some similar problems regarding overflow of document numbers, I used a trick in another
test:

{code}
IndexReader small = ...
IndexReader[] arr1 = new IndexReader[count];
Arrays.fill(arr1, small);
MultiReader intermediate = new MulitiReader(arr1);
IndexReader[] arr2 = new IndexReader[count];
Arrays.fill(arr2, intermediate);
MultiReader huge = new MulitiReader(arr2);
{code}

Producing a composite reader with count * count * small.maxDoc() docs, but spending almost
no RAM. Maybe we can do something similar here (wrapping this huge synthetic reader with SlowMultiReaderWrapper)?

                  
> re-enable test timeout, but factor in nightly, multiplier, clover
> -----------------------------------------------------------------
>
>                 Key: LUCENE-4301
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4301
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: general/test
>            Reporter: Robert Muir
>
> Having a test timeout is great (for things like test hangs), but its going to cause a
lot of failed builds until we factor in the various flags that can cause tests to run longer,
or enable longer-running tests.
> Its hard to say what the limits should be since jenkins history is pretty limited at
the moment (only 2 nightly runs history available)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message