I'm sorry I really think I'm off on my own planet. What issue are you
trying to solve? Performance, or deterministic tests? I'm concerned
with the latter and still do not understand what this has to do with
it.
On Sun, Jan 17, 2010 at 1:31 PM, Olivier Grisel
<olivier.gri...@ensta.org> wrote:
> 2010/1/17 Sean Owen <sro...@gmail.com>:
>> I think I must be missing something --
>>
>> We don't use SecureRandom directly, so what would these effects have
>> to do with slow unit tests in our project?
>
> Classloading MersenneTwisterRNG in turn class loads
> DefaultSeedGenerator which has the following static block:
>
> private static final SeedGenerator[] GENERATORS = new SeedGenerator[]
> {
> new DevRandomSeedGenerator(),
> new RandomDotOrgSeedGenerator(),
> new SecureRandomSeedGenerator()
> };
>
> And further rely upon an instance of java.security.SecureRandom for each fork.
>
> I am currently tracing a complete maven surefire run with eclipse to
> see if we actually call generateSeed in the tests. So far this is the
> case only in TransactionTreeTest which need a fix to use the test
> seed.
>
> --
> Olivier
> http://twitter.com/ogrisel - http://code.oliviergrisel.name
>
