2010/1/18 Jeff Eastman <j...@windwardsolutions.com>: > Sean Owen wrote: >> >> Could be. I took an indirect stab at mitigating possible sources of >> this issue by increasing encapsulation in the tests -- I still believe >> fields should never by non-private. This may start to surface the >> behind-the-scenes dependencies and side effects that shouldn't be >> there. But the issue, if you're right, probably concerns too much >> static stuff. >> >> What tests are failing? >> >> > > I tried -X, --error and --debug options but none gave me any more resolution > on the problem. Thinking this might be an initialization issue, I commented > out the two assertEquals statements in > ../dirichlet/TestMapReduce.testMapper() and .testReducer() and now the Maven > install runs just fine. So, it looks to me like a recent change to the way > random numbers are initialized introduced the problem. I don't know why > nobody else is seeing this, since I have not changed either of those two > tests.
Have you tried to have a look at the surefire test reports in: mahout/core/target/surefire-reports ? Failure stacktraces are stored in org.apache.mahout.*.txt files. If you want to plug eclipse to the JVM running the maven surefire tests to setup breakpoints: http://maven.apache.org/plugins/maven-surefire-plugin/examples/debugging.html -- Olivier http://twitter.com/ogrisel - http://code.oliviergrisel.name
