lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Muir <>
Subject Re: (LUCENE-3994) some nightly tests take hours
Date Tue, 17 Apr 2012 20:38:54 GMT
Digging in a bit into the slow nightlies, I think this explains a lot
(see my other email: question about seed)

I opened, but
honestly i would really prefer if we didnt have to change our tests
here, if somehow, when we do getRandom() the class's hashcode or
something like that is xored with the seed to mix it up a bit, I think
it would be ok.

I can easily fix LuceneTestCase/SolrTestCaseJ4/etc but there are many
tests that do stuff in beforeClass (e.g. build a directory), so if all
tests are 'doing the same thing' we get less predictable test times,
and less test efficiency.

This is because there is redundancy in our tests (of course), which I
think is ok, actually good, as long as these defaults are varying
per-test-class such that we get wide coverage within a single 'ant

On Tue, Apr 17, 2012 at 3:53 PM, Robert Muir <> wrote:
> I haven't looked, but i seriously doubt thats responsible at all.
> Thats just an example "crazy" one.
> More likely it got SimpleText codec :)
> On Tue, Apr 17, 2012 at 3:49 PM, Dawid Weiss
> <> wrote:
>>> Like this? :)
>> If it's correlated with the commit of RandomizedRunner then I'd check
>> if it's not that "asserting" Random instance or random() being
>> repeatedly called gazillion times. Like I said -- there is an extra
>> cost for these assertions so in tight loops (where there is no
>> possibility of Random escaping to another thread, etc.), I'd just
>> create a simple Random rnd = new Random(random().nextLong()).
>> Dawid
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> --


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message