workqueue: in ProcessPoolTaskManager use terminate(), not close().
In lib.workqueue.task.ProcessPoolTaskManager, calling the Close()
method can hang forever if a child process is hung. This method is
only called from an environment where we intend to terminate the
current process, so waiting indefinitely (or even timing out) isn't
a good choice.
This changes the Close() method to use Pool.terminate() instead of
Pool.close(), to force immediate termination.
BUG=chromium:755914
TEST=Use altered unit tests that fail and leave hung children behind
Change-Id: I3edb184230b670ec67efbea5ac042bf11ed30c92
Reviewed-on: https://chromium-review.googlesource.com/630577
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
1 file changed
