What failures do you see? The tests ought to be isolated as they (should) reserve unique temp directories in which to work. Does forkMode = once mean there's one JVM? That could be the problem, due to RNG differences. It really needs a JVM per thread.
On Sat, Aug 6, 2011 at 8:34 PM, Grant Ingersoll <[email protected]> wrote: > Granted, I'm on a slow machine, but our tests take forever to run. On an 2 > core MBP, it takes well over an hour to run all the tests (I did just order > a new MBP, so it will be faster, but it doesn't lend itself to a good OOTB > experience for people) > > One idea would be to add in parallel test execution in Maven. I think this > requires Mvn 3, but I am not sure. Another is to take a look at our tests, > especially the slow ones and see if we can speed them up. > > When I try adding in parallel tests to Maven, I get a bunch of failures in > the tests. > > I was using: > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-surefire-plugin</artifactId> > <configuration> > <forkMode>once</forkMode> > <argLine>-Xms256m -Xmx512m</argLine> > <testFailureIgnore>false</testFailureIgnore> > <redirectTestOutputToFile>true</redirectTestOutputToFile> > <parallel>classes</parallel> > <threadCount>5</threadCount> > </configuration> > </plugin> > > Anyone played around with this stuff? I suspect the failures are due to > tests stomping on each other, but I am still digging in. > > -Grant
