hi,

i tested the mercurial plugin attached to
http://jira.codehaus.org/browse/SCM-230. can somebody helb me
understanding what goes wrong where resp. what was the real thing
going on, especially:
* what directory is the whole thing going on
* what is the ecact failure and the expected result

i attaced the sample output of the testcases below ...

---------------------------------
1. without debug
---------------------------------
...
Running 
org.apache.maven.scm.provider.hg.command.changelog.HgChangeLogCommandTckTest
EXECUTING: hg init
EXECUTING: hg add
/var/tmpmvn-scm-trunk/maven-scm-providers/maven-scm-provider-hg/target/test-branch/pom.xml
/var/tmpmvn-scm-trunk/maven-scm-providers/maven-scm-provider-hg/target/test-branch/readme.txt
/var/tmpmvn-scm-trunk/maven-scm-providers/maven-scm-provider-hg/target/test-branch/src/main/java/Application.java
/var/tmpmvn-scm-trunk/maven-scm-providers/maven-scm-provider-hg/target/test-branch/src/test/java/Test.java
EXECUTING: hg commit --message "Add files to test branch"
[INFO] Removing
/var/tmpmvn-scm-trunk/maven-scm-providers/maven-scm-provider-hg/target/scm-test/working-copy
[INFO] EXECUTING: hg clone
/var/tmpmvn-scm-trunk/maven-scm-providers/maven-scm-provider-hg/target/test-branch
/var/tmpmvn-scm-trunk/maven-scm-providers/maven-scm-provider-hg/target/scm-test/working-copy
[INFO] EXECUTING: hg locate
[INFO] EXECUTING: hg log --verbose
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.552
sec <<< FAILURE!
....

----------------------------------------------------------------
2. debug mode
----------------------------------------------------------------
if i put it in debug mode i get additionally a joke message like:

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: There are test failures.
       at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
       at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
       at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
       at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
       at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
       at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
       at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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.java:403)
       at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
       at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
       ... 16 more

Reply via email to