Thanks, Sean. I run it again, and the error is reproducible as I got exactly the same error.
Thanks, James ________________________________ From: Sean Owen <[email protected]> To: [email protected] Sent: Wed, December 9, 2009 9:45:51 AM Subject: Re: mahout-0.2 release test case failed That's odd, I'm sure the tests passed at time of release since we couldn't proceed without it. I *think* you can more or less safely ignore it, but, wondering at the difference. It could be due to some differences in random number generation -- which would be a bug since the unit tests ought to use the same RNG each time. Is it reproducible? I don't see this in head, FWIW. On Wed, Dec 9, 2009 at 2:50 PM, James James <[email protected]> wrote: > Thanks again, Sean! We run Maven on linux and this time we only got one test > failed. It is a clustering test. The error message is included below. Has > anybody else run into the same error before? > > Thanks > > ------------------------------------------------------------------------------- > Test set: org.apache.mahout.clustering.kmeans.TestKmeansClustering > ------------------------------------------------------------------------------- > Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.561 sec > <<< FAILURE! > testKMeansMRJob(org.apache.mahout.clustering.kmeans.TestKmeansClustering) > Time elapsed: 10.447 sec <<< FAILURE! > junit.framework.AssertionFailedError: clusters[3] expected:<4> but was:<2> > at junit.framework.Assert.fail(Assert.java:47) > at junit.framework.Assert.failNotEquals(Assert.java:280) > at junit.framework.Assert.assertEquals(Assert.java:64) > at junit.framework.Assert.assertEquals(Assert.java:198) > at > org.apache.mahout.clustering.kmeans.TestKmeansClustering.testKMeansMRJob(TestKmeansClustering.java:423) > > > > > ________________________________ > From: Sean Owen <[email protected]> > To: [email protected] > Sent: Tue, December 8, 2009 4:58:59 PM > Subject: Re: download mahout-0.2 release > > Is it by any chance due to OutOfMemoryError? then just set > MAVEN_OPTS=-Xmx512m before running mvn. > > On Tue, Dec 8, 2009 at 10:57 PM, James James > <[email protected]> wrote: >> Thanks, Sean. I did run mvn install to try to get a mahout-0.2.jar file so I >> can put it in the library in case I want to use it. However, there are quite >> a few junits tests failed, many of which have something to do with hadoop. >> Did anybody experience the same thing before? What would be a good solution >> to build a jar file in such a situation. >> >> Thanks, James >> >> >> >> >> ________________________________ >> From: Sean Owen <[email protected]> >> To: [email protected] >> Sent: Tue, December 8, 2009 2:28:31 PM >> Subject: Re: download mahout-0.2 release >> >> You can depend on the artifacts in the Maven repository, or just run >> 'mvn install' locally to build all the .jars. Yeah I think we should >> just include the .jars next time for convenience. >> >> On Tue, Dec 8, 2009 at 8:26 PM, James James <[email protected]> >> wrote: >>> Hi, I just downloaded mahout-0.2, but could not find the libraries (.jar >>> file) needed for mahout. Is there a separate place to download these files? >>> >>> >>> Thanks, >>> >>> James >>> >>> >>> >> >> >> >> > > > >
