Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-751

hudson.tasks.junit.AbortException thrown on some maven2 projects

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: All, OS: Linux

      I'm currently using hudson with several maven2 projects. After upgrading from
      version 1.126 to 1.129, all of the projects which run JUnit tests fail after the
      integration-test phase. The projects are all configured to monitor svn targets,
      and the maven goals being executed are "clean deploy". The following is the
      stack trace:

      [HUDSON] Recording test results
      [HUDSON] Archiving
      /usr/local/hudson/.hudson/jobs/Platform-Trunk/workspace/platform-trunk/client-plugin/pom.xml
      [HUDSON] Archiving
      /usr/local/hudson/.hudson/jobs/Platform-Trunk/workspace/platform-trunk/client-plugin/target/client-
      plugin-0.8.19-SNAPSHOT.jar
      [HUDSON] Archiving
      /usr/local/hudson/.hudson/jobs/Platform-Trunk/workspace/platform-trunk/client-plugin/target/client-plugin-0.8.19-SNAPSHOT-sources.jar
      [INFO] ------------------------------------------------------------------------

      [ERROR] FATAL ERROR
      [INFO] ------------------------------------------------------------------------
      [INFO] Test reports were found but none of them are new. Did tests run? For
      example,
      /usr/local/hudson/.hudson/jobs/Platform-Trunk/workspace/platform-trunk/client-plugin/target/surefire-reports/TEST-
      net.mobio.qname.LocalNameMapTest.xml is 0 seconds old

      [INFO] ------------------------------------------------------------------------
      [INFO] Trace
      hudson.tasks.junit.AbortException: Test reports were found but none of them are
      new. Did tests run? For example,
      /usr/local/hudson/.hudson/jobs/Platform-Trunk/workspace/platform-trunk/client-plugin/target/surefire-reports/TEST-
      net.mobio.qname.LocalNameMapTest.xml is 0 seconds old

      at hudson.tasks.junit.TestResult.<init>(TestResult.java:90)
      at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:67)
      at hudson.maven.PluginManagerInterceptor.postExecute
      (PluginManagerInterceptor.java:111)
      at
      hudson.maven.agent.PluginManagerInterceptor$1MojoConfig.callPost(PluginManagerInterceptor.java:102)
      at
      hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java
      :133)
      at
      org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
      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.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:35)
      at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:327)
      at org.apache.maven.DefaultMaven.execute
      (DefaultMaven.java:120)
      at org.apache.maven.cli.MavenCli.main(MavenCli.java:263)
      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 hudson.maven.agent.Main.launch(Main.java:89)
      at hudson.maven.MavenBuild$Builder.call(MavenBuild.java:172)
      at hudson.maven.MavenBuild$Builder.call
      (MavenBuild.java:140)
      at hudson.remoting.UserRequest.perform(UserRequest.java:69)
      at hudson.remoting.UserRequest.perform(UserRequest.java:23)
      at hudson.remoting.Request$2.run(Request.java:178)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
      (ThreadPoolExecutor.java:650)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
      at java.lang.Thread.run(Thread.java:595)
      [INFO] ------------------------------------------------------------------------

      [INFO] Total time: 25 seconds
      [INFO] Finished at: Thu Aug 16 10:33:06 PDT 2007
      [INFO] Final Memory: 12M/29M
      [INFO] ------------------------------------------------------------------------
      finished: FAILURE

          [JENKINS-751] hudson.tasks.junit.AbortException thrown on some maven2 projects

          lozdvc5 added a comment -

          Created an attachment (id=82)
          sample project with integration and unit tests

          lozdvc5 added a comment - Created an attachment (id=82) sample project with integration and unit tests

          I couldn't reproduce the problem, but I think I understand the error condition
          now, so I made a change in 1.135 that should fix this.

          Kohsuke Kawaguchi added a comment - I couldn't reproduce the problem, but I think I understand the error condition now, so I made a change in 1.135 that should fix this.

          lozdvc5 added a comment -

          Verified that this works with projects using surefire plugin in two maven phases.

          lozdvc5 added a comment - Verified that this works with projects using surefire plugin in two maven phases.

          Frank Mueller added a comment -

          Problem seems to be back in 1.565.3

          Started a multi module maven build with parameter

          -Dmaven.test.failure.ignore=true
          

          Jasmine tests will not be executed but jenkins still tries to get the test results.

          [INFO] --- jasmine-maven-plugin:1.3.1.4:test (default) @ lh-ress-ui ---
          [INFO] Skipping Jasmine Specs
          [JENKINS] Zeichne Testergebnisse auf
          hudson.AbortException: Test reports were found but none of them are new. Did tests run? 
          For example, /home/jenkinslocal/jenkins-jobs/workspace/lufthansa-reactor-master-SNAPSHOT-NEW/lufthansa-ress-ui/target/jasmine/TEST-jasmine.xml is 44 Jahre old
          
          	at hudson.tasks.junit.TestResult.parse(TestResult.java:213)
          	at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:148)
          	at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:628)
          	at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:610)
          	at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:306)
          	at org.apache.maven.eventspy.internal.EventSpyDispatcher.onEvent(EventSpyDispatcher.java:108)
          	at org.apache.maven.eventspy.internal.EventSpyExecutionListener.mojoSucceeded(EventSpyExecutionListener.java:131)
          	at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
          	at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
          	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:227)
          	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:317)
          	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
          	at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132)
          	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
          	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          	at java.lang.reflect.Method.invoke(Method.java:606)
          	at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
          	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
          	at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181)
          	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
          	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          	at java.lang.reflect.Method.invoke(Method.java:606)
          	at hudson.maven.Maven3Builder.call(Maven3Builder.java:134)
          	at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
          	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
          	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
          	at hudson.remoting.Request$2.run(Request.java:328)
          	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
          	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
          	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
          	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
          	at java.lang.Thread.run(Thread.java:745)
          [INFO] 
          

          Frank Mueller added a comment - Problem seems to be back in 1.565.3 Started a multi module maven build with parameter -Dmaven.test.failure.ignore= true Jasmine tests will not be executed but jenkins still tries to get the test results. [INFO] --- jasmine-maven-plugin:1.3.1.4:test ( default ) @ lh-ress-ui --- [INFO] Skipping Jasmine Specs [JENKINS] Zeichne Testergebnisse auf hudson.AbortException: Test reports were found but none of them are new . Did tests run? For example, /home/jenkinslocal/jenkins-jobs/workspace/lufthansa-reactor-master-SNAPSHOT-NEW/lufthansa-ress-ui/target/jasmine/TEST-jasmine.xml is 44 Jahre old at hudson.tasks.junit.TestResult.parse(TestResult.java:213) at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:148) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:628) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:610) at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:306) at org.apache.maven.eventspy.internal.EventSpyDispatcher.onEvent(EventSpyDispatcher.java:108) at org.apache.maven.eventspy.internal.EventSpyExecutionListener.mojoSucceeded(EventSpyExecutionListener.java:131) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:227) 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:317) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang. Thread .run( Thread .java:745) [INFO]

          Frank Mueller added a comment - - edited

          Aditional Info:

          If I add the parameter

          -DskipTests=true
          

          Everything works fine.

          But in our Case we would only prevent integration-test from run. Therefore we have something like skipTests=false and maven.test.skip=true.

          Frank Mueller added a comment - - edited Aditional Info: If I add the parameter -DskipTests= true Everything works fine. But in our Case we would only prevent integration-test from run. Therefore we have something like skipTests=false and maven.test.skip=true.

          Daniel Beck added a comment -

          Just file a new issue. What are the chances the cause is actually the same as in this seven years old issue?

          Daniel Beck added a comment - Just file a new issue. What are the chances the cause is actually the same as in this seven years old issue?

          Frank Mueller added a comment -

          Because the original cause was never mentioned here i cannot assume this.

          The cause here is that there is a check if skipTests is set to true and prevent the plugin from gathering the data. But it skipTests=false and maven.test.skip=true the data gathering will take place even for plugins that are not runnig (like jasmine).

          Frank Mueller added a comment - Because the original cause was never mentioned here i cannot assume this. The cause here is that there is a check if skipTests is set to true and prevent the plugin from gathering the data. But it skipTests=false and maven.test.skip=true the data gathering will take place even for plugins that are not runnig (like jasmine).

          Frank Mueller added a comment -

          Created new issue.

          Frank Mueller added a comment - Created new issue.

          Frank Mueller added a comment -

          closed

          Frank Mueller added a comment - closed

            Unassigned Unassigned
            lozdvc5 lozdvc5
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: