Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #59 - Prevent failure when Child processes cannot be retrieved due to the system shutdown #172

Merged

Conversation

oleg-nenashev
Copy link
Member

@oleg-nenashev oleg-nenashev commented Dec 24, 2016

Edited by @NextTurn: Fixes #59 and JENKINS-22692

This is a bit hackish way, which still terminates the spawned process even in the case of the ongoing system shutdown. In Jenkins project it should help with enforced termination of Windows agents, which somehow leaves hanging connections on the master side. Maybe this issue has been already solved in other way on the remoting side, but there is no confirmations from users....

@reviewbybees

@ghost
Copy link

ghost commented Dec 24, 2016

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

@oleg-nenashev oleg-nenashev merged commit 852b8b6 into winsw:master Dec 27, 2016
@nxtn nxtn modified the milestones: 2.0.1, 2.0.0 Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[JENKINS-22692] - Shutdown exception. Cannot get Child Pids
2 participants