Thanks all. I too noticed that everything worked with the Apple JVM on my
mac. I will
checkout trunk, run tests and get back to you all.What is confusing is
that
the test almost passes. The numbers are right, just assigned to the wrong
variables.
In general, is this type of a post better
Hello all,
Well I have checked out trunk (
Last Changed Author: ssc
Last Changed Rev: 1145213
Last Changed Date: 2011-07-11 11:48:16 -0400 (Mon, 11 Jul 2011)
)
and am getting many many failing tests due to a
org.apache.hadoop.security.UserGroupInformation (initialization failure)
This is a
I'm not seeing this error -- can you please post more about the stack trace?
Coming from Hadoop, it seems more like an environment problem.
On Mon, Jul 11, 2011 at 5:46 PM, Marc Millstone millst...@gmail.com wrote:
Hello all,
Well I have checked out trunk (
Last Changed Author: ssc
Last
Sean,
I am seeing stack-traces such as
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
Yeah that's not it. It's just internal exceptions because a test failed.
What were you referring to by org.apache.hadoop.security.UserGroupInformation
(initialization failure) ? That sounds closer to a problem.
In the output of the failed unit test results, the reason for failure is
given as
testLoad(org.apache.mahout.df.mapreduce.partial.InterResultsTest):
com.sun.security.auth.UnixPrincipal
testStore(org.apache.mahout.df.mapreduce.partial.InterResultsTest):
That's no good. Sounds like some local file system permissions issue? Are
there any restrictions on /tmp? maybe blow away anything that looks Hadoop-
or Mahout-related there.
You can dig into core/target/surefire-reports and find a file with all
output for every test. It will surely have more
Ok. I am starting to think this could be a IBM JVM thing
after finding this JIRA: https://issues.apache.org/jira/browse/HADOOP-7211
Could it be that something changed between trunk and .5 that caused this
issue to manifest itself in different ways?
In .5, we just got the wrong answer and in
I strongly suspect it is because we updated to Hadoop 0.20.203.0. 0.5
depended on 0.20.2. You could locally go back to depending on 0.20.2; it
ought to still work fine with the previous version.
On Mon, Jul 11, 2011 at 8:14 PM, Marc Millstone millst...@gmail.com wrote:
Ok. I am starting to
Ok. Let me play with this some more. I appreciate your help.
In .5, under the IBM JVM we still get the Unit test failure in PFPGrowth
though. It seems
to be a true failure too, not an initialization issue.
I am now going to install the Sun JVM locally on my cluster and link against
that to
Good News: The offending unit tests passes with the combination of
IBM JVM + Mahout Trunk + Hadoop 0.20.2
To recap:
IBM JVM + Mahout .5 + Hadoop 0.20.2 fails with the error
testStartParallelFPGrowth(org.apache.mahout.fpm.pfpgrowth.PFPGrowthTest):
expected:{[D=0, E=1, A=0, B=0, C]=1} but
It sounds like the actual test failure does not occur in HEAD, so sounds
like whatever it is is already fixed or rendered moot.
The issue about Hadoop 0.20.203.0 is a Hadoop issue at best, and looks like
they're already tracking it. I think it should be fixed of course, but it's
not a Mahout
You're welcome, and welcome to add to the wiki as you see fit:
https://cwiki.apache.org/MAHOUT/mahout-wiki.html
Maybe one of the Installation/Setup pages is a good home for a note?
On Mon, Jul 11, 2011 at 8:53 PM, Marc Millstone millst...@gmail.com wrote:
Awesome. I agree entirely with your
The tests passed at 0.5, and now at trunk. I have tested on Apple JVMs and I
assume Jenkins uses a Sun JVM.
I doubt it is a JVM issue, though possible. But I don't see what it has to
do with being a product?
On Sat, Jul 9, 2011 at 6:11 AM, Lance Norskog goks...@gmail.com wrote:
Mahout releases
Hello all,
I have started to play around with Mahout today. During installation,
the unit test testStartParallelFPGrowth is failing. (I am not sure whether
to send this post
here or to the developer list).
Adding the -e option to maven, we get the culprit
Failed tests:
Did you check out the Mahout trunk? That test might be broken now; it
should have worked in the 0.5 source release (checkpoint, really).
On Fri, Jul 8, 2011 at 5:41 PM, Marc Millstone millst...@gmail.com wrote:
Hello all,
I have started to play around with Mahout today. During installation,
No, I downloaded the src from the Mahout website with the .5 checkpoint.
(file mahout-distribution-0.5-src.tar.gz)
I will try to throw a Sun JVM into my home directory on the cluster and try
to isolate the failed unit test from the JVM choice.
As you can see from the failed test, the answer is
Mahout releases are not product releases (at this point), but more
milestones denoting accomplishment. If there is a problem with the IBM
JVM and the Mahout trunk, that is important. I'm sure that whatever
the problem, it is the same in 0.5 and the trunk, but please test with
the trunk.
On Fri,
18 matches
Mail list logo
