-
Notifications
You must be signed in to change notification settings - Fork 76
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
On windows, send sigkill to process if it exceeds its alloted time #79
Conversation
I haven't had any luck with the tests, but I'm 👍 on this change. Can you add a spec so we don't regress? |
Yeah spec and 👍 |
Code looks sane, would like a regression test. What we do for *nix is create a process that sleeps for a very long time (like 100s or more) and then set the timeout very low, like 1s, then check if the process exists after rescuing the timeout error. |
There's also some associated bugs in the chef repo about windows timeouts being ignored which can be closed after this is merged. |
Timeouts did not work correctly on windows because we do not kill or abandon the process. What was happening was a timeout condition was getting correctly detected, and an exception was being raised. However, before the exception could propogate, whatever the process was writing was fully read until it closed its FD.
2fc9d56
to
ffec9cd
Compare
@tyler-ball @randomcamel @danielsdeleo Added a test |
ffec9cd
to
4f425ea
Compare
👍 |
On windows, send sigkill to process if it exceeds its alloted time
On windows, send sigkill to process if it exceeds its alloted time
Timeouts did not work correctly on windows because we do not kill or
abandon the process.
What was happening was a timeout condition was getting correctly detected,
and an exception was being raised. However, before the exception could
propagate, whatever the process was writing was fully read until it closed its FD.
@randomcamel said he was fixing up the tests
cc @btm @adamedx @randomcamel @opscode/client-engineers