• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • Jenkins 2.138.2
      Java 10.0.2 Azul Zulu
      Maven 3.6.0
      Maven Integration Plugin 3.1.2
      Launched With: java --add-modules java.xml.bind -jar $JENKINS_INSTALL/jenkins.war --enable-future-java --httpPort=8080

      I'm running my integration tests in a maven project using "mvn integration-test". The tests succeed but the job is marked as failed.  This is surely related to Java 10 in some way.

       

      [pool-1-thread-4 for channel id=7] INFO org.apache.maven.plugin.failsafe.IntegrationTestMojo - 
      [pool-1-thread-4 for channel id=7] INFO org.apache.maven.plugin.failsafe.IntegrationTestMojo - 
      [pool-1-thread-4 for channel id=7] INFO org.apache.maven.plugin.failsafe.IntegrationTestMojo - Results:[pool-1-thread-4 for channel id=7] INFO org.apache.maven.plugin.failsafe.IntegrationTestMojo - 
      [pool-1-thread-4 for channel id=7] WARNING org.apache.maven.plugin.failsafe.IntegrationTestMojo - Tests run: 66, Failures: 0, Errors: 0, Skipped: 3
      [pool-1-thread-4 for channel id=7] INFO org.apache.maven.plugin.failsafe.IntegrationTestMojo - 
      [JENKINS] Recording test results
      [WARNING] Attempt to (de-)serialize anonymous class hudson.maven.reporters.SurefireArchiver$2; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
      [WARNING] Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenArtifactArchiver$2; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
      [WARNING] Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenFingerprinter$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
      [pool-1-thread-4 for channel id=7] INFO org.apache.maven.cli.event.ExecutionEventLogger - ------------------------------------------------------------------------
      [pool-1-thread-4 for channel id=7] INFO org.apache.maven.cli.event.ExecutionEventLogger - BUILD SUCCESS
      [pool-1-thread-4 for channel id=7] INFO org.apache.maven.cli.event.ExecutionEventLogger - ------------------------------------------------------------------------
      [pool-1-thread-4 for channel id=7] INFO org.apache.maven.cli.event.ExecutionEventLogger - Total time:  01:24 min
      [pool-1-thread-4 for channel id=7] INFO org.apache.maven.cli.event.ExecutionEventLogger - Finished at: 2018-11-09T10:45:37-08:00
      [pool-1-thread-4 for channel id=7] INFO org.apache.maven.cli.event.ExecutionEventLogger - ------------------------------------------------------------------------
      Waiting for Jenkins to finish collecting data
      [JENKINS] Archiving /jenkins/jobs/SubApiFunctionalTest/workspace/pom.xml to sub-api/1.0.20181109-663/sub-api-1.0.20181109-663.pom
      [JENKINS] Archiving /jenkins/jobs/SubApiFunctionalTest/workspace/target/sub-api-1.0.20181109-663.jar to sub-api/1.0.20181109-663/sub-api-1.0.20181109-663.jar
      channel stopped
      FATAL: null
      java.lang.ClassNotFoundException: java.lang.UNIXProcess 
          at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466) 
          at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:566) 
          at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499) 
          at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:565) 
          at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499) 
          at java.base/java.lang.Class.forName0(Native Method) 
          at java.base/java.lang.Class.forName(Class.java:291) 
          at hudson.util.ProcessTree$UnixReflection.<clinit>(ProcessTree.java:778)
      Caused: java.lang.LinkageError 
          at hudson.util.ProcessTree$UnixReflection.<clinit>(ProcessTree.java:789) 
          at hudson.util.ProcessTree$UnixProcess.kill(ProcessTree.java:726) 
          at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:747) 
          at hudson.util.ProcessTree$Unix.killAll(ProcessTree.java:666) 
          at hudson.Launcher$LocalLauncher.kill(Launcher.java:954)
          at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:510) 
          at hudson.model.Run.execute(Run.java:1819) 
          at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) 
          at hudson.model.ResourceController.execute(ResourceController.java:97) 
          at hudson.model.Executor.run(Executor.java:429)

      A previous step in this (old-style) pipeline is an identically configured job that runs "mvn deploy" and that works just fine.  The only difference I can see is that this step is configured with "Build Other Projects (manual step)" as as Post-Build Action, whereas the job that succeeds uses "Trigger Parameterized Build on Other Projects".

       

      I just realized I have also seen this on a Gradle build.  The build ends with

      BUILD SUCCESSFUL in 8m 45s
      5 actionable tasks: 5 executed
      Build step 'Invoke Gradle script' changed build result to SUCCESS
      FATAL: null
      java.lang.ClassNotFoundException: java.lang.UNIXProcess
      etc etc etc, same stack trace as above

      This build immediately triggers another so I think the Post-Build Action is likely a red herring.

          [JENKINS-54561] Job fails even though it succeeded: Java 10

          Daniel Beck added a comment -

          oleg_nenashev Are we even attempting to work on Java 10, or does this need to happen on Java 11 for us to care?

          Daniel Beck added a comment - oleg_nenashev Are we even attempting to work on Java 10, or does this need to happen on Java 11 for us to care?

          Oleg Nenashev added a comment -

          Hi. This issue would happen on Java 11 as well. Good news is that it was fixed in Jenkins 2.144, see JENKINS-46523.  Although stacktraces are a bit different, this issue should be fixed as well. The fix was not backported to the 2.138.x LTS baseline, but it will appear in the next one which will be released in 1 month or so.

          W.r.t Java 10 support, yes we do not plan to officially support it. Jenkins JEP-211 was rescoped to Java 11 only. OTOH Java 10 will likely work as well. In order to run with Java 10/11, Jenkins version 2.147 should be used (the most recent functional fix).

          kenwdelong Thanks for the report anyway! We will appreciate any testing and feedback for Java 10 or Java 11. https://jenkins.io/blog/2018/06/17/running-jenkins-with-java10-11/ reflects the current guidelines for running it (recent weekly WARs can be used as well tho)

          Oleg Nenashev added a comment - Hi. This issue would happen on Java 11 as well. Good news is that it was fixed in Jenkins 2.144, see JENKINS-46523 .  Although stacktraces are a bit different, this issue should be fixed as well. The fix was not backported to the 2.138.x LTS baseline, but it will appear in the next one which will be released in 1 month or so. W.r.t Java 10 support, yes we do not plan to officially support it. Jenkins JEP-211 was rescoped to Java 11 only. OTOH Java 10 will likely work as well. In order to run with Java 10/11, Jenkins version 2.147 should be used (the most recent functional fix). kenwdelong Thanks for the report anyway! We will appreciate any testing and feedback for Java 10 or Java 11. https://jenkins.io/blog/2018/06/17/running-jenkins-with-java10-11/ reflects the current guidelines for running it (recent weekly WARs can be used as well tho)

            Unassigned Unassigned
            kenwdelong Ken DeLong
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: