lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] Updated: (LUCENE-2652) Rethink LocalizedTestCaseRunner with JUnit 4 - Clover OOM
Date Sat, 18 Sep 2010 15:58:34 GMT


Simon Willnauer updated LUCENE-2652:

    Attachment: LUCENE-2652.patch

really i think the two runners (LocalizedTestCase/MultiCodecTestCase) are obselete anyway,
you can run any junit test under any locale/codec, and we select locale, timezone, and codec
randomly by default.
Yeah I agree that we should fix that and get rid of them. I also think we should apply a quick
fix to make builds on hudson pass again. Yet, you patch changes lots of files - the patch
I attached is less intrusive and has the same effect.

Lets commit that and do a real fix within the next days. Thoughts?

> 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