Details
-
Bug
-
Status: Fixed but Unreleased (View Workflow)
-
Major
-
Resolution: Duplicate
-
Jenkins ver. 1.566m Java 7u25, Windows Server 2008 master, Debian & Ubuntu slaves
-
-
Jenkins 2.60.3
Description
Jenkins failed some test on 2 configurations out of a 5-configuration matrix build, with the other 3 builds completing normally. Both failed slaves leave no additional information for diagnosing the root cause:
13:49:24 Started by upstream project "fast-tests" build number 920 13:49:24 originally caused by: 13:49:24 Started by user User 13:49:24 FATAL: null 13:49:24 java.lang.NullPointerException 13:49:24 at hudson.model.Slave.createLauncher(Slave.java:359) 13:49:24 at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:559) 13:49:24 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:476) 13:49:24 at hudson.model.Run.execute(Run.java:1710) 13:49:24 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) 13:49:24 at hudson.model.ResourceController.execute(ResourceController.java:88) 13:49:24 at hudson.model.Executor.run(Executor.java:231)
JENKINS-21999 seemed to be a similar issue but the line numbers have changed and that issue was fixed, whereas this issue still occurs.
Attachments
Issue Links
- duplicates
-
JENKINS-38527 Slave#createLauncher relies on autoboxing and can thrown NPE
-
- Resolved
-
- relates to
-
JENKINS-38527 Slave#createLauncher relies on autoboxing and can thrown NPE
-
- Resolved
-
-
JENKINS-46067 Pipeline task scheduled on uninitialized node
-
- Open
-
- links to
It's weird how a job can be scheduled for a node before it could be determined whether it's Unix.