Spoke too soon of course, some tests fail strangely locally: /u01/eclipse/eclipse-mahout-workspace/mahout-svn/core/src/test/java/org/apache/mahout/ga/watchmaker/EvalMapperTest.java:[48,25] type parameter org.apache.hadoop.io.LongWritable is not within its bound
/u01/eclipse/eclipse-mahout-workspace/mahout-svn/core/src/test/java/org/apache/mahout/ga/watchmaker/EvalMapperTest.java:[48,92] type parameter org.apache.hadoop.io.LongWritable is not within its bound Looks like this was discussed way back in http://issues.apache.org/jira/browse/MAHOUT-127, but for the life of my I can'y figure out why I'm running into it now. On Sun, Jan 17, 2010 at 8:38 PM, Drew Farris <drew.far...@gmail.com> wrote: > On Sun, Jan 17, 2010 at 2:55 PM, Sean Owen <sro...@gmail.com> wrote: >> Am I right that running tests in 1 JVM instead of n JVMs helps >> mitigate this? because I just committed that change. >> > > I just updated to HEAD, and this seems to have fixed the problem. Unit > tests are completing in times in-line with those reported by the tests > themselves. > > Since this was happening at class loading time, running all of the > tests in a single VM does mitigate this becuase less forks mean less > entropy drain and there is more time to collect entropy between forks. >
