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
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:600)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test
failures.
and
at
org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:74)
at
org.apache.maven.plugin.surefire.SurefirePlugin.writeSummary(SurefirePlugin.java:644)
at
org.apache.maven.plugin.surefire.SurefirePlugin.executeAfterPreconditionsChecked(SurefirePlugin.java:640)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:102)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
These traces seem to be simple test failure traces I think.
How can I better get information to help debug this? I am running mvn -e -X
install in the core directory.
Everything is compiling perfectly, I am just seeing these unit test failures
(now with the reason
given above, with an initialization failure). In an earlier post, I list
all
of my version information. With version .5 of Mahout, the unit test failure
is actually something
where the output does not match expected output. With trunk, it is due to
these user issues.
(Sorry I can't do more on my own. I am not a java hacker/mvn guru, as I
spend most of my time in Scala).
Thanks in advance!
marc
On Mon, Jul 11, 2011 at 11:21 AM, Sean Owen <[email protected]> wrote:
> 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 <[email protected]>
> wrote:
>
> > 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 different failure than with the .5 src.
> >
> > I appreciate your help in advance. I am not certain as to how to best go
> > about fixing this (but again, I am more than happy to try
> > anything/read anything, etc to help).
> >
> > Thanks!
> > marc
> >
> >
> >
> > On Mon, Jul 11, 2011 at 8:51 AM, Marc Millstone <[email protected]>
> > wrote:
> >
> > > 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 to be placed on user or dev?
> > >
> > >
> > > On Sat, Jul 9, 2011 at 12:50 AM, Sean Owen <[email protected]> wrote:
> > >
> > >> 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 <[email protected]>
> > wrote:
> > >>
> > >> > 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.
> > >> >
> > >> >
> > >>
> > >
> > >
> >
>
