You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kudu.apache.org by "Todd Lipcon (Code Review)" <ge...@ip-10-146-233-104.ec2.internal> on 2016/01/15 08:59:13 UTC

[kudu-CR] client_samples-test: wait for processes to exit after kill -9

Hello Adar Dembo,

I'd like you to do a code review.  Please visit

    http://gerrit.cloudera.org:8080/1795

to review the following change.

Change subject: client_samples-test: wait for processes to exit after kill -9
......................................................................

client_samples-test: wait for processes to exit after kill -9

kill -9 doesn't guarantee immediate delivery of the signal to the target
process. In particular, if the process is in an uninterruptible sleep
state inside the kernel, it may be some small amount of time before
it actually exits. During this time, it's possible it could proceed
and create new files on disk, etc. This might cause occasional failures
of the 'rm -rf' call following the kills in this test case -- a behavior
we're seeing occasionally on Jenkins.

Change-Id: I2ba711723b327168be942405b5354ca57c106043
---
M src/kudu/client/client_samples-test.sh
1 file changed, 2 insertions(+), 0 deletions(-)


  git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/95/1795/1
-- 
To view, visit http://gerrit.cloudera.org:8080/1795
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: newchange
Gerrit-Change-Id: I2ba711723b327168be942405b5354ca57c106043
Gerrit-PatchSet: 1
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Todd Lipcon <to...@apache.org>
Gerrit-Reviewer: Adar Dembo <ad...@cloudera.com>