[JIRA] (JENKINS-38354) Failure to resume a wrapper step leads to hanging build

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 After JENKINS-39134 we are not using Guice in this way so this is probably obsolete.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38354  
 
 
  Failure to resume a wrapper step leads to hanging build   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You

[JIRA] (JENKINS-38354) Failure to resume a wrapper step leads to hanging build

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38354  
 
 
  Failure to resume a wrapper step leads to hanging build   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
Labels: 
 robustness  triaged-2018-11  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-38354) Failure to resume a wrapper step leads to hanging build

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38354  
 
 
  Failure to resume a wrapper step leads to hanging build   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 workflow-cps-plugin  
 
 
Created: 
 2016/Sep/19 7:16 PM  
 
 
Labels: 
 robustness  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 Take this PR and comment out optional=true which allows ConsoleLogFilterStep.Execution to be safely restored. Run Jenkins with it, create and attach a JNLP agent, create a Pipeline script running something like 

 

node('agent-name') {
  checkout([$class: 'MercurialSCM', source: 'http://hg.netbeans.org/main-silver/'])
  ant 'build'
}
 

 (or just any long-running Ant project) and start running. Once it is running Ant, restart Jenkins. After the restart, a bit more output will be printed and then the build will hang, irrecoverably. workflow-durable-task-step PR 17 will allow you to see that there is a Guice-related exception. But after that any attempt to abort the build will simply print an error: the sh step already got stopped, so exited with 143 (SIGTERM), but then the consoleLogFilter step's StepContext thinks it too is already finished, and will not allow it to be finished "again". The virtual thread dump says it is in consoleLogFilter. Only a hard kill suffices at this point. Is there some way to force the CPS VM thread to treat the current StepExecution as a lost cause and really throw its exception up the call stack?