-
Notifications
You must be signed in to change notification settings - Fork 91
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
CA-327382: reap child processes #456
Conversation
This caused XSI-474 and other reported customer issues. Signed-off-by: Mark Syms <mark.syms@citrix.com>
os.killpg(pid, signal.SIGKILL) | ||
raise AbortException("Aborting due to signal") | ||
if timeOut and time.time() - startTime > timeOut: | ||
os.killpg(pid, signal.SIGKILL) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps we could tidyup by having a resultFlag.clearall() in the finally?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps we could tidyup by having a resultFlag.clearall() in the finally.
Do we still care at that point? If we entered the finally: as the result of an exception, the exception will be re-thrown when the finally completes.
wait_pid, rc = os.waitpid(pid, os.WNOHANG) | ||
if wait_pid == 0: | ||
time.sleep(2) | ||
count += 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
docs say that an OSError can be raised by os.waitpid, do we want to catch it or bomb out?
This caused XSI-474 and other reported customer issues.
Signed-off-by: Mark Syms mark.syms@citrix.com