[ https://issues.apache.org/jira/browse/LUCENE-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler reopened LUCENE-3184: ----------------------------------- There are some problems now in nightly builds with OOMs (boith 3.x and trunk). We can do either: - reduce some nightly settings - raise -Xmx if nightly=true, maybe dependent on number of iterations, too? > add LuceneTestCase.rarely()/LuceneTestCase.atLeast() > ---------------------------------------------------- > > Key: LUCENE-3184 > URL: https://issues.apache.org/jira/browse/LUCENE-3184 > Project: Lucene - Java > Issue Type: Test > Reporter: Robert Muir > Fix For: 3.3, 4.0 > > Attachments: LUCENE-3184.patch > > > in LUCENE-3175, the tests were sped up a lot by using reasonable number of > iterations normally, but cranking up for NIGHTLY. > we also do crazy things more 'rarely' for normal builds (e.g. simpletext, > payloads, crazy merge params, etc) > also, we found some bugs by doing this, because in general our parameters are > too fixed. > however, it made the code look messy... I propose some new methods: > instead of some crazy code in your test like: > {code} > int numdocs = (TEST_NIGHTLY ? 1000 : 100) * RANDOM_MULTIPLIER; > {code} > you use: > {code} > int numdocs = atLeast(100); > {code} > this will apply the multiplier, also factor in nightly, and finally add some > random fudge... so e.g. in local runs its sometimes 127 docs, sometimes 113 > docs, etc. > additionally instead of code like: > {code} > if ((TEST_NIGHTLY && random.nextBoolean()) || (random.nextInt(20) == 17)) { > {code} > you do > {code} > if (rarely()) { > {code} > which applies NIGHTLY and also the multiplier (logarithmic growth). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org