>> > Unit tests should generally be using a fixed seed and not need to load a > secure seed from dev/random. I would say that RandomUtils is probably the > problem here. The secure seed should be loaded lazily only if the test seed > is not in use.
The problem, as I see it, is that the uncommons-math package start initializing a random seed as soon as you touch it, whether you need it or not. RandomUtils can only avoid this by avoiding uncommons-math in unit test mode. > > > > -- > Ted Dunning, CTO > DeepDyve >
