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

Avoid racing reparent in zombie-reaping integration test #120

Merged
merged 1 commit into from
Mar 29, 2016

Conversation

tgross
Copy link
Contributor

@tgross tgross commented Mar 29, 2016

At any given time we may have up to 1 zombie parented to PID1 (it has been reparented but not yet reaped) and 1 zombie not yet parented to PID1. We can't test any more precisely than this without racing the kernel reparenting mechanism (do_exit()).

Also updated the test to capture the ps tree only once so that we don't log something different from what we tested.

cc @justenwalker per our discussion in #119

At any given time we may have up to 1 zombie parented to PID1 (it has been
reparented but not yet reaped) and 1 zombie not yet parented to PID1. We can't
test any more precisely than this without racing the kernel reparenting
mechanism (`do_exit()`).

Also updated the test to capture the ps tree only once so that we don't log
something different from what we tested.
@justenwalker
Copy link
Contributor

LGTM

@tgross tgross merged commit ca59479 into TritonDataCenter:master Mar 29, 2016
@tgross tgross deleted the zombie_reap_race branch April 4, 2017 15:46
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.

2 participants