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.
- duplicates
-
JENKINS-46523 FATAL: Could not initialize class hudson.util.ProcessTree$UnixReflection
-
- Resolved
-
