[ https://issues.apache.org/jira/browse/LUCENE-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12911039#action_12911039 ]
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: https://issues.apache.org/jira/browse/LUCENE-2652 > 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|http://www.lucidimagination.com/search/document/ae20885bf5baedc5/build_failed_in_hudson_lucene_3_x_116#7ed351341152ee2d] > 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 locale) -- 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org