[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title
Thomas Goeppel updated an issue
Jenkins / JENKINS-26137
Mysterious serialization errors
Change By:
Thomas Goeppel
A flow which just had{code}node('...') {sh 'echo hi'}{code}waited for a node matching the label. I restarted Jenkins after changing something so that the label would be available. The shell step ran, but then the flow failed with{code:none}...Running: Allocate node : EndRunning: End of Workflowjava.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:890) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1062) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java: 1018 10S18 ) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:884) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:584) at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:58) at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:111) at org.jenkinsci.plugins.workflow.support.pickles.serialization.RiverWriter.close(RiverWriter.java:145) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:341) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:323) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:297) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:71) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:183) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:181) 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) at org.jenkinsci.plugins.workflow.cps.CpsVmThread.run(CpsVmThread.java:21)Caused by: an exception which occurred: in field task in object java.util.ArrayList@401ac88Finished: FAILURE{code}{{CpsStepContext.getThread}} then began complaining that{code:none}no thread 2 among []{code}as the {{DurableTaskStep$Execution.run}} kept on running.It is not apparent from this stack trace why something is trying to serialize the job.Observed also in PR 21; https://github.com/jenkinsci/workflow-plugin/commit/a594618516a22e9e8bcd016808ca487efee80fff fixed it. Turned out in that case that the culprit was {{ExecutorPickle}}. But why could the error message not say that? It only said {{field task}}, which was not enough information.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java http://jenkins-ci.org/commit/workflow-cps-plugin/f383df6b4df20d790df09123489c63f55d048896 Log: Checking sources for other possible restartability bugs as in JENKINS-26149 . RetryStep looks suspicious but apparently works. PushdStep cannot be tested due to a mysterious error noted in JENKINS-26137. Originally-Committed-As: cc76ee2256279676b4858cae95244585feceebaa Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java http://jenkins-ci.org/commit/workflow-multibranch-plugin/fe863c4a5ba855d65cd68588a71e5293f0bdf641 Log: JENKINS-26137 At least during restarting tests, serialization errors seem to be due to there being no PickleFactory’s installed. Merely calling PickleFactory.all() from the RiverWriter constructor, rather than later, seems to let PushdStepTest.restarting pass ( JENKINS-26051 ). Additionally asserting that there are in fact some factories loaded, since there is sure to be trouble if there are not. Also need to wait for the build to finish ( JENKINS-26399 ). Originally-Committed-As: 3d3fa348ed9c34e4492b2733802bc47416824e30 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java http://jenkins-ci.org/commit/workflow-multibranch-plugin/e2f865e9f5ad0ade62076df4ca51da245183cfc5 Log: Checking sources for other possible restartability bugs as in JENKINS-26149 . RetryStep looks suspicious but apparently works. PushdStep cannot be tested due to a mysterious error noted in JENKINS-26137. Originally-Committed-As: cc76ee2256279676b4858cae95244585feceebaa Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/963cfbe1131efe28165d45b6da566b0271c684a2 Log: Merge pull request #33 from jenkinsci/JENKINS-26137-no-pickle-factories Make a test involving Jenkins restart pass Originally-Committed-As: 9186a512e4ecf901217bc3f4b219810322e84db9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/89c28b4fca0eb81cf369ff699f7a4d801fc83e83 Log: JENKINS-26137 At least during restarting tests, serialization errors seem to be due to there being no PickleFactory’s installed. Merely calling PickleFactory.all() from the RiverWriter constructor, rather than later, seems to let PushdStepTest.restarting pass ( JENKINS-26051 ). Additionally asserting that there are in fact some factories loaded, since there is sure to be trouble if there are not. Also need to wait for the build to finish ( JENKINS-26399 ). Originally-Committed-As: 3d3fa348ed9c34e4492b2733802bc47416824e30 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java http://jenkins-ci.org/commit/workflow-scm-step-plugin/0aec9ed07c5fe959d08b5355c9353108143f1d58 Log: Checking sources for other possible restartability bugs as in JENKINS-26149 . RetryStep looks suspicious but apparently works. PushdStep cannot be tested due to a mysterious error noted in JENKINS-26137. Originally-Committed-As: cc76ee2256279676b4858cae95244585feceebaa Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java http://jenkins-ci.org/commit/workflow-scm-step-plugin/7583bf18eda2968bebc10024b52aee00a3614149 Log: JENKINS-26137 At least during restarting tests, serialization errors seem to be due to there being no PickleFactory’s installed. Merely calling PickleFactory.all() from the RiverWriter constructor, rather than later, seems to let PushdStepTest.restarting pass ( JENKINS-26051 ). Additionally asserting that there are in fact some factories loaded, since there is sure to be trouble if there are not. Also need to wait for the build to finish ( JENKINS-26399 ). Originally-Committed-As: 3d3fa348ed9c34e4492b2733802bc47416824e30 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/RetryStepExecution.java http://jenkins-ci.org/commit/workflow-basic-steps-plugin/5a9db4b7a32a7985d4b63a5dad2170d3cc8fc0e6 Log: Checking sources for other possible restartability bugs as in JENKINS-26149 . RetryStep looks suspicious but apparently works. PushdStep cannot be tested due to a mysterious error noted in JENKINS-26137. Originally-Committed-As: cc76ee2256279676b4858cae95244585feceebaa Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java http://jenkins-ci.org/commit/workflow-basic-steps-plugin/85812e78a3ab6c837b59002082e30bdc16294688 Log: JENKINS-26137 At least during restarting tests, serialization errors seem to be due to there being no PickleFactory’s installed. Merely calling PickleFactory.all() from the RiverWriter constructor, rather than later, seems to let PushdStepTest.restarting pass ( JENKINS-26051 ). Additionally asserting that there are in fact some factories loaded, since there is sure to be trouble if there are not. Also need to wait for the build to finish ( JENKINS-26399 ). Originally-Committed-As: 3d3fa348ed9c34e4492b2733802bc47416824e30 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/PushdStep.java http://jenkins-ci.org/commit/workflow-basic-steps-plugin/8f03c17d07933c822b2f5a9caa3d25fc059e972c Log: Merge pull request #33 from jenkinsci/JENKINS-26137-no-pickle-factories Make a test involving Jenkins restart pass Originally-Committed-As: 9186a512e4ecf901217bc3f4b219810322e84db9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: support/src/main/java/org/jenkinsci/plugins/workflow/support/pickles/serialization/RiverWriter.java http://jenkins-ci.org/commit/workflow-support-plugin/18ad074331b663f565633bf4fa8523ac68dc1a69 Log: JENKINS-26137 At least during restarting tests, serialization errors seem to be due to there being no PickleFactory’s installed. Merely calling PickleFactory.all() from the RiverWriter constructor, rather than later, seems to let PushdStepTest.restarting pass ( JENKINS-26051 ). Additionally asserting that there are in fact some factories loaded, since there is sure to be trouble if there are not. Also need to wait for the build to finish ( JENKINS-26399 ). Originally-Committed-As: 3d3fa348ed9c34e4492b2733802bc47416824e30 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title
Ali Sadik Kumlali commented on JENKINS-26137
Re: Mysterious serialization errors
I came across the same error with Jenkins 2 - alpha 3. XmlSlurper().parseText() seems to trigger it:
New Item -> Pipeline, Pipeline script
node {
...
def pomXml = readFile('pom.xml')
bat "echo before XmlSlurper().parseText()"
def parsedPomXml = new XmlSlurper().parseText(pomXml)
// Following line fails
bat "echo after XmlSlurper().parseText()"
}
Job's Console Output
[Pipeline] readFile
[Pipeline] bat
[MyPipelineWithPipelineScript] Running batch script
d:\workspace\projects\jenkins2_pipeline\home\workspace\MyPipelineWithPipelineScript>echo before XmlSlurper().parseText()
before XmlSlurper().parseText()
[Pipeline] bat
[MyPipelineWithPipelineScript] Running batch script
[Pipeline] } //node
[Pipeline] Allocate node : End
[Pipeline] End of Pipeline
java.io.NotSerializableException: groovy.util.slurpersupport.NodeChild
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860)
...
at org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:271)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:976)
...
at org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
...
at org.jenkinsci.plugins.workflow.support.pickles.serialization.RiverWriter.writeObject(RiverWriter.java:132)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:371)
...
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
...
at java.lang.Thread.run(Thread.java:745)
Caused by: an exception which occurred:
in field locals
in field caller
in field e
in field program
in field threads
in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@7138f387
Finished: FAILURE
Add Comment
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title Jesse Glick commented on JENKINS-26137 Re: Mysterious serialization errors Specifically demo can fail if you /restart at just the wrong point: … [longerTests] Running org.jenkinsci.plugins.workflow.demo.AppTest [Workflow] } //node [Workflow] Allocate node : End [Workflow] } //parallel [Workflow] } //node [Workflow] } //parallel [Workflow] End of Workflow java.lang.IllegalStateException: JENKINS-26137: Jenkins is shutting down at org.jenkinsci.plugins.workflow.support.pickles.serialization.RiverWriter.(RiverWriter.java:92) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:345) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:331) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:306) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:74) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:183) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:181) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-26137 Mysterious serialization errors Change By: Jesse Glick Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title Jesse Glick commented on JENKINS-26137 Re: Mysterious serialization errors Observed during a build with safeRestart in 1.8: java.lang.IllegalStateException: JENKINS-26137: Jenkins is shutting down at org.jenkinsci.plugins.workflow.support.pickles.serialization.RiverWriter.init(RiverWriter.java:93) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:342) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:303) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:71) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:180) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:178) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
SCM/JIRA link daemon commented on JENKINS-26137 Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/PushdStep.java support/src/main/java/org/jenkinsci/plugins/workflow/support/pickles/serialization/RiverWriter.java http://jenkins-ci.org/commit/workflow-plugin/9186a512e4ecf901217bc3f4b219810322e84db9 Log: Merge pull request #33 from jenkinsci/JENKINS-26137-no-pickle-factories Make a test involving Jenkins restart pass Compare: https://github.com/jenkinsci/workflow-plugin/compare/dd5eaf7aa09c...9186a512e4ec This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
SCM/JIRA link daemon commented on JENKINS-26137 Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: pom.xml src/test/java/org/jenkinsci/plugins/credentialsbinding/impl/BindingStepTest.java http://jenkins-ci.org/commit/credentials-binding-plugin/707c1d82c1efa0c42e8daff6d487196c2c6dacbd Log: Trying to test JENKINS-26051 across restarts but blocked by JENKINS-26137. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
SCM/JIRA link daemon commented on JENKINS-26137 Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/pickles/serialization/RiverWriter.java http://jenkins-ci.org/commit/workflow-plugin/3d3fa348ed9c34e4492b2733802bc47416824e30 Log: JENKINS-26137 At least during restarting tests, serialization errors seem to be due to there being no PickleFactory’s installed. Merely calling PickleFactory.all() from the RiverWriter constructor, rather than later, seems to let PushdStepTest.restarting pass (JENKINS-26051). Additionally asserting that there are in fact some factories loaded, since there is sure to be trouble if there are not. Also need to wait for the build to finish (JENKINS-26399). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
SCM/JIRA link daemon commented on JENKINS-26137 Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/RetryStepExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java http://jenkins-ci.org/commit/workflow-plugin/cc76ee2256279676b4858cae95244585feceebaa Log: Checking sources for other possible restartability bugs as in JENKINS-26149. RetryStep looks suspicious but apparently works. PushdStep cannot be tested due to a mysterious error noted in JENKINS-26137. Compare: https://github.com/jenkinsci/workflow-plugin/compare/87553e9e6e35...cc76ee225627 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Jesse Glick
created JENKINS-26137
Mysterious serialization errors
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
workflow-plugin
Created:
17/Dec/14 5:36 PM
Description:
A flow which just had
node('...') {sh 'echo hi'}
waited for a node matching the label. I restarted Jenkins after changing something so that the label would be available. The shell step ran, but then the flow failed with
...
Running: Allocate node : End
Running: End of Workflow
java.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:890)
at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1062)
at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1018)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:884)
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:584)
at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:58)
at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:111)
at org.jenkinsci.plugins.workflow.support.pickles.serialization.RiverWriter.close(RiverWriter.java:145)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:341)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:323)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:297)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:71)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:183)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:181)
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)
at org.jenkinsci.plugins.workflow.cps.CpsVmThread.run(CpsVmThread.java:21)
Caused by: an exception which occurred:
in field task
in object java.util.ArrayList@401ac88
Finished: FAILURE
CpsStepContext.getThread then began complaining that
no thread 2 among []
as the DurableTaskStep$Execution.run kept on running.
It is not apparent from this stack trace why something is trying to serialize the job.
Observed also in PR 21; https://github.com/jenkinsci/workflow-plugin/commit/a594618516a22e9e8bcd016808ca487efee80fff fixed it. Turned out in that case that the culprit was ExecutorPickle. But why could the error message not say that? It only said field task, which was not enough information.
Project:
Jenkins
Labels:
robustness
Priority:
Minor
Reporter:
Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
