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

Robert Muir updated LUCENE-3264:
--------------------------------

    Attachment: LUCENE-3264.patch

attached is a patch with the improvements discussed, also just a couple test 
speedups (seems to shave off about a minute for me, setting me at 2minutes).

Note I explicitly didnt change any of the ones that extend BaseTestTopK here... 
these tests are more complicated but I think we need to adjust this one to do 
more work on the nightly, and less work on regular builds (currently each test 
method in every class that extends this looks like it indexes up to 20000 * 4 = 
80000 documents).

I know these are the sluggish ones, but I'd really prefer to handle this 
separately because they are complicated.


> crank up faceting module tests
> ------------------------------
>
>                 Key: LUCENE-3264
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3264
>             Project: Lucene - Java
>          Issue Type: Test
>          Components: modules/facet
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>             Fix For: 3.4, 4.0
>
>         Attachments: LUCENE-3264.patch, LUCENE-3264.patch
>
>
> The faceting module has a large set of good tests.
> lets switch them over to use all of our test infra (randomindexwriter, random 
> iwconfig, mockanalyzer, newDirectory, ...)
> I don't want to address multipliers and atLeast() etc on this issue, I think 
> we should follow up with that on a separate issue, that also looks at speed 
> and making sure the nightly build is exhaustive.
> for now, lets just get the coverage in, it will be good to do before any 
> refactoring.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to