1) Choose a Windows7/8/10 node and mark it offline in its configuration page
2) then mark it online
3) Create a job attached to this node with the Windows command: notepad.exe
4) Start your job, check that Notepad is started (dont close).
5) Cancel the build of the job and see that Notepad is still open.
On the windows node, if you manually restart the agent, this fixes the "kill behavior".
the problem also happens for an accidental deconnection/reconnection (that how we notificed that, because randomly it seems that the ProcessTreeKiller did not work anymore and it seemed that it happened after networks issues between the server and the node)
- is related to
-
JENKINS-24319 Windows slave dying during build - unsatisfied link error
-
- Reopened
-
[JENKINS-31706] ProcessTreeKiller broken for Windows when node went offline/online
Stephane Gallès
created issue -
Stephane Gallès
made changes -
| Description |
Original:
1) Choose a Windows7/8/10 node and mark it offline in its configuration page 2) then mark it online 3) Create a job attached to this node with the Windows command: notepad.exe 4) Start your job, check that Notepad is started (dont close). 5) Cancel the build of the job and see that Notepad is still open. On the windows node, if you manually restart the agent, this fixes the "kill behavior". the problem also happens for an accidental deconnection/reconnection (that how we've notificed that, because randomly it seems that the ProcessTreeKiller did not work anymore and it seemed that it happened after networks issues between the server and the node) |
New:
1) Choose a Windows7/8/10 node and mark it offline in its configuration page 2) then mark it online 3) Create a job attached to this node with the Windows command: notepad.exe 4) Start your job, check that Notepad is started (dont close). 5) Cancel the build of the job and see that Notepad is still open. On the windows node, if you manually restart the agent, this fixes the "kill behavior". the problem also happens for an accidental deconnection/reconnection (that how we notificed that, because randomly it seems that the ProcessTreeKiller did not work anymore and it seemed that it happened after networks issues between the server and the node) |
| Workflow | Original: JNJira [ 167146 ] | New: JNJira + In-Review [ 182610 ] |
| Labels | New: winp |
| Link | New: This issue is related to JENKINS-24319 [ JENKINS-24319 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |