• Type: Bug
• Resolution: Duplicate
• Priority: Major
• Component/s: durable-task-plugin
• Labels:

  • durability
  • pipeline
  • triaged-2018-11
  • windows
• Environment:

  Windows Server 2016 Datacenter, Jenkins 2.107.2, Durable Task 1.22, workflow-support 2.18, workflow-cps 2.51, workflow-job 2.21

[JENKINS-51145] PowerShell pipeline step does not seem to be durable

Gabriel Loewen created issue - 2018-05-04 18:31

Gabriel Loewen made changes - 2018-05-04 18:32

Description

Original: While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code.   {code:java} node ('Windows') {     powershell '''     while (1) {         write-host "Testing"         Start-Sleep 1     }     ''' } {code} Console output:     {noformat} Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Resuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restart Waiting to resume part of Test Durability #5: ??? Testing Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Ready to run at Fri May 04 17:40:19 UTC 2018 Testing Testing Testing Testing Testing [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code -1 Finished: FAILURE{noformat}   I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed. At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step. [~svanoort], let me know if you need any more details and if you can assist in this investigation.

New: While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code.   {code:java} node ('Windows') {     powershell '''     while (1) {         write-host "Testing"         Start-Sleep 1     }     ''' } {code} Console output:     {noformat} Started by user Gabriel Loewen Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on WinHost in C:\Program Files (x86)\Jenkins\workspace\Test Durability [Pipeline] { [Pipeline] powershell [Test Durability] Running PowerShell script Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Resuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restart Waiting to resume part of Test Durability #5: ??? Testing Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Ready to run at Fri May 04 17:40:19 UTC 2018 Testing Testing Testing Testing Testing [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code -1 Finished: FAILURE{noformat}   I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed. At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step. [~svanoort], let me know if you need any more details and if you can assist in this investigation.

Gabriel Loewen made changes - 2018-05-04 18:33

Description

Original: While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code.   {code:java} node ('Windows') {     powershell '''     while (1) {         write-host "Testing"         Start-Sleep 1     }     ''' } {code} Console output:     {noformat} Started by user Gabriel Loewen Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on WinHost in C:\Program Files (x86)\Jenkins\workspace\Test Durability [Pipeline] { [Pipeline] powershell [Test Durability] Running PowerShell script Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Resuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restart Waiting to resume part of Test Durability #5: ??? Testing Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Ready to run at Fri May 04 17:40:19 UTC 2018 Testing Testing Testing Testing Testing [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code -1 Finished: FAILURE{noformat}   I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed. At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step. [~svanoort], let me know if you need any more details and if you can assist in this investigation.

New: While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code.  Job definition: {code:java} node ('Windows') {     powershell '''     while (1) {         write-host "Testing"         Start-Sleep 1     }     ''' } {code} Console output: {noformat} Started by user Gabriel Loewen Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on WinHost in C:\Program Files (x86)\Jenkins\workspace\Test Durability [Pipeline] { [Pipeline] powershell [Test Durability] Running PowerShell script Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Resuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restart Waiting to resume part of Test Durability #5: ??? Testing Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Ready to run at Fri May 04 17:40:19 UTC 2018 Testing Testing Testing Testing Testing [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code -1 Finished: FAILURE{noformat}   I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed. At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step. [~svanoort], let me know if you need any more details and if you can assist in this investigation.

Gabriel Loewen made changes - 2018-05-04 18:33

Description

Original: While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code.  Job definition: {code:java} node ('Windows') {     powershell '''     while (1) {         write-host "Testing"         Start-Sleep 1     }     ''' } {code} Console output: {noformat} Started by user Gabriel Loewen Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on WinHost in C:\Program Files (x86)\Jenkins\workspace\Test Durability [Pipeline] { [Pipeline] powershell [Test Durability] Running PowerShell script Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Resuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restart Waiting to resume part of Test Durability #5: ??? Testing Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Ready to run at Fri May 04 17:40:19 UTC 2018 Testing Testing Testing Testing Testing [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code -1 Finished: FAILURE{noformat}   I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed. At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step. [~svanoort], let me know if you need any more details and if you can assist in this investigation.

New: While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code. Job definition: {code:java} node ('Windows') {     powershell '''     while (1) {         write-host "Testing"         Start-Sleep 1     }     ''' } {code} Console output: {noformat} Started by user Gabriel Loewen Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on WinHost in C:\Program Files (x86)\Jenkins\workspace\Test Durability [Pipeline] { [Pipeline] powershell [Test Durability] Running PowerShell script Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Resuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restart Waiting to resume part of Test Durability #5: ??? Testing Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Ready to run at Fri May 04 17:40:19 UTC 2018 Testing Testing Testing Testing Testing [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code -1 Finished: FAILURE{noformat}   I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed. At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step. [~svanoort], let me know if you need any more details and if you can assist in this investigation.

Gabriel Loewen made changes - 2018-05-04 18:34

Description

Original: While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code. Job definition: {code:java} node ('Windows') {     powershell '''     while (1) {         write-host "Testing"         Start-Sleep 1     }     ''' } {code} Console output: {noformat} Started by user Gabriel Loewen Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on WinHost in C:\Program Files (x86)\Jenkins\workspace\Test Durability [Pipeline] { [Pipeline] powershell [Test Durability] Running PowerShell script Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Resuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restart Waiting to resume part of Test Durability #5: ??? Testing Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Ready to run at Fri May 04 17:40:19 UTC 2018 Testing Testing Testing Testing Testing [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code -1 Finished: FAILURE{noformat}   I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed. At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step. [~svanoort], let me know if you need any more details and if you can assist in this investigation.

New: While running a PowerShell pipeline step I triggered a graceful shutdown, while also monitoring the powershell.exe process on the Jenkins host. The PowerShell process unexpectedly crashed, and the job failed with a -1 exit code. Job definition: {code:java} node ('Windows') {     powershell '''     while (1) {         write-host "Testing"         Start-Sleep 1     }     ''' } {code} Console output: {noformat} Started by user Gabriel Loewen Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on WinHost in C:\Program Files (x86)\Jenkins\workspace\Test Durability [Pipeline] { [Pipeline] powershell [Test Durability] Running PowerShell script Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Testing Resuming build at Fri May 04 17:40:07 UTC 2018 after Jenkins restart Waiting to resume part of Test Durability #5: ??? Testing Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Waiting to resume part of Test Durability #5: WinHost is offline Ready to run at Fri May 04 17:40:19 UTC 2018 Testing Testing Testing Testing Testing [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code -1 Finished: FAILURE{noformat}   I ran the same test again and this time it hung, even though the PowerShell process seems to have crashed. At this point I do not know how to debug the issue, and what can be done to ensure durability in the powershell pipeline step. [~svanoort], [~teilo], let me know if you need any more details and if you can assist in this investigation.

Gabriel Loewen made changes - 2018-05-04 18:52

Environment

Original: Windows Server 2016 Datacenter, Jenkins 2.107.2, Durable Task 1.22

New: Windows Server 2016 Datacenter, Jenkins 2.107.2, Durable Task 1.22, workflow-support 2.18, workflow-cps 2.51, workflow-job 2.21

Gabriel Loewen made changes - 2018-05-09 16:09

Assignee

Original: Gabriel Loewen [ gabloe ]

Gabriel Loewen made changes - 2018-05-09 16:09

Labels

New: durability pipeline windows

Gabriel Loewen made changes - 2018-05-09 16:11

Link

New: This issue is related to JENKINS-27617 [ JENKINS-27617 ]

jang hyemi (Inactive) made changes - 2018-06-22 01:16

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Vivek Pandey made changes - 2018-11-16 17:50

Labels

Original: durability pipeline windows

New: durability pipeline triaged-2018-11 windows

Load more newer history items