[ 
https://issues.apache.org/jira/browse/LUCENE-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Muir updated LUCENE-2532:
--------------------------------

    Attachment: LUCENE-2532.patch

ok, hopefully this is just my screwup, but just in case: i want to get uwe or 
someone to confirm :)

I started converting some test cases to use this, and got some failures in 
TestNumericRangeQuery64:
{noformat}
    [junit] Testsuite: org.apache.lucene.search.TestNumericRangeQuery64
    [junit] Testcase: 
testRange_8bit(org.apache.lucene.search.TestNumericRangeQuery64): FAILED
    [junit] Distinct term number is equal for all query types expected:<494> 
but was:<493>
    [junit] junit.framework.AssertionFailedError: Distinct term number is equal 
for all query types expected:<494> but was:<493>
    [junit]     at 
org.apache.lucene.search.TestNumericRangeQuery64.testRange(TestNumericRangeQuery64.java:159)
    [junit]     at 
org.apache.lucene.search.TestNumericRangeQuery64.testRange_8bit(TestNumericRangeQuery64.java:167)
...
[junit] ------------- Standard Output ---------------
[junit] NOTE: random static seed of testclass 'testRange_8bit' was: 
7879034790334081579
{noformat}

to reproduce, just plug in the seed to the beforeClass method:
{code}
Random random = newStaticRandom(TestNumericRangeQuery64.class, 
7879034790334081579L);
{code}


> improve test coverage of multi-segment indices
> ----------------------------------------------
>
>                 Key: LUCENE-2532
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2532
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 3.1, 4.0
>
>         Attachments: LUCENE-2532.patch, LUCENE-2532.patch
>
>
> Simple patch that adds a test-only helper class, RandomIndexWriter, that lets 
> you add docs, but it will randomly do things like use a different merge 
> policy/scheduler, flush by doc count instead of RAM, flush randomly (so we 
> get multi-segment indices) but also randomly optimize in the end (so we also 
> sometimes test single segment indices).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to