You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by do...@emc.com on 2007/05/12 09:30:27 UTC
test failures
I am getting a test failure message from maven:
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:560)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:143)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoFailureException: There are test
failures.
at
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.j
ava:425
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:539)
... 16 more
This happens on teh build machine. It works fine on all the other
developer's machine. I have confirmed that the versions of maven, the
settings.xml are the same. This is with maven 2.0.6.
Why won't maven print the real reason for the error? This stack trace is
useless. mvn -X doesn't provide any information that is useful either.
How do I debug this?
-Moiz
RE: test failures
Posted by do...@emc.com.
Thanks for the response.
I tried that, here's what I got:
-----Original Message-----
From: Andrew Williams [mailto:andy@handyande.co.uk]
Sent: Saturday, May 12, 2007 12:40 AM
To: Maven Users List
Subject: Re: test failures
they are logged to a file, do
mvn test -Dsurefire.useFile=false
to log them to stdout - no need for -e or -X
Andy
On 12 May 2007, at 00:30, dohadwala_moiz@emc.com wrote:
> I am getting a test failure message from maven:
>
> [INFO] Trace
> org.apache.maven.BuildFailureException: There are test failures.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (Default
> LifecycleExecutor.java:560)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif
> ec
> ycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> (DefaultL
> ifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand
> le
> Failures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
> s(
> DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> (DefaultLifec
> ycleExecutor.java:143)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
> 125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.jav
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessor
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoFailureException: There are
> test failures.
> at
> org.apache.maven.plugin.surefire.SurefirePlugin.execute
> (SurefirePlugin.j
> ava:425
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo
> (DefaultPluginMa
> nager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (Default
> LifecycleExecutor.java:539)
> ... 16 more
>
> This happens on teh build machine. It works fine on all the other
> developer's machine. I have confirmed that the versions of maven, the
> settings.xml are the same. This is with maven 2.0.6.
>
> Why won't maven print the real reason for the error? This stack trace
> is useless. mvn -X doesn't provide any information that is useful
> either.
>
> How do I debug this?
>
> -Moiz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: RE: test failures
Posted by Seth Mason <se...@slackorama.com>.
Just to clarify, the txt and xml report files are written out to
./target/surefire-reports/.
SETH
On 5/14/07, Thorsten Heit <th...@gmx.de> wrote:
> Hi,
>
> > I am still blocked, does anyone have any more ideas on this? I am
> > running with the latest version of maven 2.0.6.
>
> The last time I used the surefire plugin for JUnit tests, it created a text and a XML file for each executed test somewhere in the ./target subdirectory. The text files contain the outputs from the unit tests, so if some of them fail on your machine, you should control them to see why and/or where which tests fail.
>
>
> HTH
>
> Thorsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
SETH
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: RE: test failures
Posted by Thorsten Heit <th...@gmx.de>.
Hi,
> I am still blocked, does anyone have any more ideas on this? I am
> running with the latest version of maven 2.0.6.
The last time I used the surefire plugin for JUnit tests, it created a text and a XML file for each executed test somewhere in the ./target subdirectory. The text files contain the outputs from the unit tests, so if some of them fail on your machine, you should control them to see why and/or where which tests fail.
HTH
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: test failures
Posted by do...@emc.com.
Hello,
I am still blocked, does anyone have any more ideas on this? I am
running with the latest version of maven 2.0.6.
Thanks,
-Moiz
-----Original Message-----
From: dohadwala, moiz
Sent: Saturday, May 12, 2007 8:58 AM
To: dohadwala, moiz; Maven Users List
Subject: RE: test failures
Sorry, that one got away:
I tried setting that property:
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date [INFO]
[resources:testResources] [INFO] Using default encoding to copy filtered
resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date [INFO]
[surefire:test] [INFO] Surefire report directory:
D:\luntbuild\projects\has\has\common\target\surefire-reports
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] There are test failures.
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch [INFO]
------------------------------------------------------------------------
[INFO] Total time: 9 seconds
[INFO] Finished at: Sat May 12 08:55:57 PDT 2007 [INFO] Final Memory:
6M/11M [INFO]
------------------------------------------------------------------------
Thanks,
-Moiz
-----Original Message-----
From: dohadwala, moiz
Sent: Saturday, May 12, 2007 8:57 AM
To: 'Maven Users List'
Subject: RE: test failures
Thanks for the response.
I tried that, here's what I got:
-----Original Message-----
From: Andrew Williams [mailto:andy@handyande.co.uk]
Sent: Saturday, May 12, 2007 12:40 AM
To: Maven Users List
Subject: Re: test failures
they are logged to a file, do
mvn test -Dsurefire.useFile=false
to log them to stdout - no need for -e or -X
Andy
On 12 May 2007, at 00:30, dohadwala_moiz@emc.com wrote:
> I am getting a test failure message from maven:
>
> [INFO] Trace
> org.apache.maven.BuildFailureException: There are test failures.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (Default
> LifecycleExecutor.java:560)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif
> ec
> ycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> (DefaultL
> ifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand
> le
> Failures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
> s(
> DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> (DefaultLifec
> ycleExecutor.java:143)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
> 125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.jav
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessor
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoFailureException: There are
> test failures.
> at
> org.apache.maven.plugin.surefire.SurefirePlugin.execute
> (SurefirePlugin.j
> ava:425
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo
> (DefaultPluginMa
> nager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (Default
> LifecycleExecutor.java:539)
> ... 16 more
>
> This happens on teh build machine. It works fine on all the other
> developer's machine. I have confirmed that the versions of maven, the
> settings.xml are the same. This is with maven 2.0.6.
>
> Why won't maven print the real reason for the error? This stack trace
> is useless. mvn -X doesn't provide any information that is useful
> either.
>
> How do I debug this?
>
> -Moiz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: test failures
Posted by do...@emc.com.
Sorry, that one got away:
I tried setting that property:
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
D:\luntbuild\projects\has\has\common\target\surefire-reports
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] There are test failures.
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 9 seconds
[INFO] Finished at: Sat May 12 08:55:57 PDT 2007
[INFO] Final Memory: 6M/11M
[INFO]
------------------------------------------------------------------------
Thanks,
-Moiz
-----Original Message-----
From: dohadwala, moiz
Sent: Saturday, May 12, 2007 8:57 AM
To: 'Maven Users List'
Subject: RE: test failures
Thanks for the response.
I tried that, here's what I got:
-----Original Message-----
From: Andrew Williams [mailto:andy@handyande.co.uk]
Sent: Saturday, May 12, 2007 12:40 AM
To: Maven Users List
Subject: Re: test failures
they are logged to a file, do
mvn test -Dsurefire.useFile=false
to log them to stdout - no need for -e or -X
Andy
On 12 May 2007, at 00:30, dohadwala_moiz@emc.com wrote:
> I am getting a test failure message from maven:
>
> [INFO] Trace
> org.apache.maven.BuildFailureException: There are test failures.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (Default
> LifecycleExecutor.java:560)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif
> ec
> ycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> (DefaultL
> ifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand
> le
> Failures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
> s(
> DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> (DefaultLifec
> ycleExecutor.java:143)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
> 125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.jav
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessor
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoFailureException: There are
> test failures.
> at
> org.apache.maven.plugin.surefire.SurefirePlugin.execute
> (SurefirePlugin.j
> ava:425
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo
> (DefaultPluginMa
> nager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (Default
> LifecycleExecutor.java:539)
> ... 16 more
>
> This happens on teh build machine. It works fine on all the other
> developer's machine. I have confirmed that the versions of maven, the
> settings.xml are the same. This is with maven 2.0.6.
>
> Why won't maven print the real reason for the error? This stack trace
> is useless. mvn -X doesn't provide any information that is useful
> either.
>
> How do I debug this?
>
> -Moiz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: test failures
Posted by Andrew Williams <an...@handyande.co.uk>.
they are logged to a file, do
mvn test -Dsurefire.useFile=false
to log them to stdout - no need for -e or -X
Andy
On 12 May 2007, at 00:30, dohadwala_moiz@emc.com wrote:
> I am getting a test failure message from maven:
>
> [INFO] Trace
> org.apache.maven.BuildFailureException: There are test failures.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (Default
> LifecycleExecutor.java:560)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif
> ec
> ycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
> (DefaultL
> ifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand
> le
> Failures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
> s(
> DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> (DefaultLifec
> ycleExecutor.java:143)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
> 125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.jav
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessor
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoFailureException: There are
> test
> failures.
> at
> org.apache.maven.plugin.surefire.SurefirePlugin.execute
> (SurefirePlugin.j
> ava:425
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo
> (DefaultPluginMa
> nager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
> (Default
> LifecycleExecutor.java:539)
> ... 16 more
>
> This happens on teh build machine. It works fine on all the other
> developer's machine. I have confirmed that the versions of maven, the
> settings.xml are the same. This is with maven 2.0.6.
>
> Why won't maven print the real reason for the error? This stack
> trace is
> useless. mvn -X doesn't provide any information that is useful either.
>
> How do I debug this?
>
> -Moiz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org