Hi
I've noticed that TestCodecs takes an insanely long time to run on my
machine - between 35-40 seconds. Is that expected?
The reason why it runs so long, seems to be that its threads make (each)
4000 iterations ... is that really required to ensure correctness?
Shai
It's also slow because it repeats all the tests for each of the core
codecs (standard, sep, pulsing, intblock).
I think it's fine to reduce the number of iterations -- just make sure
there's no seed to newRandom() so the distributing testing is
"effective".
Mike
On Fri, Apr 9, 2010 at 12:43 AM,
I have found it useful to keep two lists of tests: the slow tests and
the fast tests. Maybe the TestSuite feature would work for this
purpose?
An @SlowTest annotation would be even better. JUnit might have a tool
to do this filtering.
On Fri, Apr 9, 2010 at 2:49 AM, Michael McCandless
wrote:
> I
See you already did that Mike :). Thanks ! now the tests run for 2s.
Shai
On Fri, Apr 9, 2010 at 12:49 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> It's also slow because it repeats all the tests for each of the core
> codecs (standard, sep, pulsing, intblock).
>
> I think it's f
Yah :)
TestStressIndexing2 is another slow one... I'll go fix it...
Mike
On Thu, Apr 15, 2010 at 2:15 AM, Shai Erera wrote:
> See you already did that Mike :). Thanks ! now the tests run for 2s.
>
> Shai
>
> On Fri, Apr 9, 2010 at 12:49 PM, Michael McCandless
> wrote:
>>
>> It's also slow beca
