lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Commented: (LUCENE-2652) Rethink LocalizedTestCaseRunner with JUnit 4 - Clover OOM
Date Sat, 18 Sep 2010 16:03:33 GMT


Robert Muir commented on LUCENE-2652:

bq. Yet, you patch changes lots of files

Right, but long term we should remove these runners anyway.
So maybe we should delete the RunWiths *and* delete the runner code.

These runners are obselete and weaker than our general test support itself:
* the MultiCodecRunner cannot set parameters for the codecs, but LuceneTestCase can do this
* The LocalizedRunner cannot set timezone (this runner is used by lots of tests), but LuceneTestCase
can do this

> Rethink LocalizedTestCaseRunner with JUnit 4 - Clover OOM
> ---------------------------------------------------------
>                 Key: LUCENE-2652
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Test
>          Components: Tests
>            Reporter: Simon Willnauer
>             Fix For: 3.1, 4.0
>         Attachments: LUCENE-2652.patch, LUCENE-2652.patch
> As a spinn off from this [conversation|]
we should rethink the way how we execute testcases with different locals since glover reports
appears to throw OOM errors b/c Junit treats each local as a single test case run.
> Here are some options:
> * select the local at random only run the test with a single local
> * set the local via system property -Dtest.locale=en.EN
> * run with the default locale only -Dtest.skiplocale=true
> * one from the above but only if instrumented with clover (let common tests run all the

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:
For additional commands, e-mail:

View raw message