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

NPE from SandboxContinuable.run0 after restart

XMLWordPrintable

      In this build I observed

      ...
Running in Durability level: PERFORMANCE_OPTIMIZED
...
Resuming build at ... after Jenkins restart
[Pipeline] End of Pipeline

GitHub has been notified of this commit's build result

java.lang.NullPointerException
	at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:43)
	at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:331)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:82)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:243)
	at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:231)
	at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)
	at ...
Finished: FAILURE

      The flow graph is also missing. Not sure what happened here.

          [JENKINS-50407] NPE from SandboxContinuable.run0 after restart

          Jesse Glick created issue -
          Jesse Glick made changes -
          Remote Link New: This issue links to "PR 215 (Web Link)" [ 20321 ]

          Jesse Glick added a comment -

          svanoort claimed a possible link to a couple of other bugs under investigation.

          Jesse Glick added a comment - svanoort claimed a possible link to a couple of other bugs under investigation.
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-49686 [ JENKINS-49686 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-50199 [ JENKINS-50199 ]

          Sam Van Oort added a comment -

          I'll upgrade that from "possible" to guaranteed, knowing that the flow graph is missing too. That's a pipeline that was not cleanly persisted in performance optimized mode – and yet it is trying to resume (when it should be forbidden).

          I'm armor-plating all the resumption & completion-state logic just to try to make this a bit more failsafe.

          Sam Van Oort added a comment - I'll upgrade that from "possible" to guaranteed, knowing that the flow graph is missing too. That's a pipeline that was not cleanly persisted in performance optimized mode – and yet it is trying to resume (when it should be forbidden). I'm armor-plating all the resumption & completion-state logic just to try to make this a bit more failsafe.

          Jesse Glick added a comment -

          In Review perhaps?

          Jesse Glick added a comment - In Review perhaps?
          Sam Van Oort made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Sam Van Oort made changes -
          Assignee New: Sam Van Oort [ svanoort ]
          Sam Van Oort made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]

            svanoort Sam Van Oort
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: