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

bpo-26762: test_multiprocessing detects dangling per test case class #2841

Merged
merged 1 commit into from
Jul 24, 2017
Merged

bpo-26762: test_multiprocessing detects dangling per test case class #2841

merged 1 commit into from
Jul 24, 2017

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Jul 24, 2017

bpo-26762: test_multiprocessing now detects dangling processes and
threads per test case classes:

  • setUpClass()/tearDownClass() of mixing classes now checks if
    multiprocessing.process._dangling or threading._dangling was
    modified to detect "dangling" processses and threads.
  • ManagerMixin.tearDownClass() now also emits a warning if it still
    as more than one active child process after 5 seconds.
  • tearDownModule() now checks for dangling processes and threads
    before the cleanup.

https://bugs.python.org/issue26762

@mention-bot
Copy link

@Haypo, thanks for your PR! By analyzing the history of the files in this pull request, we identified @benjaminp, @shibturn and @pitrou to be potential reviewers.

@vstinner
Copy link
Member Author

@pitrou: Would you mind to review this change? I'm not sure that it works as expected.

First I tried tearDown(), but test_multiprocessing uses multiple inheritance and it's tricky to order correctly the cleanup code.

Proposed PR uses tearDownClass() on the 3 mixin classes. It seems like these tearDownClass() class methods are called after the tearDownClass() of test classes like _TestPool.

@vstinner
Copy link
Member Author

Ah. It seems like we have to fix a few warnings before being able to merge this PR:

Warning -- multiprocessing.process._dangling was modified by test_multiprocessing_spawn
  Before: <_weakrefset.WeakSet object at 0x2b3610354330>
  After:  <_weakrefset.WeakSet object at 0x2b360fefaf60>

@vstinner vstinner changed the title bpo-26762: test_multiprocessing calls reap_children() bpo-26762: test_multiprocessing detects dangling per test case class Jul 24, 2017
bpo-26762: test_multiprocessing now detects dangling processes and
threads per test case classes:

* setUpClass()/tearDownClass() of mixin classes now check if
  multiprocessing.process._dangling or threading._dangling was
  modified to detect "dangling" processses and threads.
* ManagerMixin.tearDownClass() now also emits a warning if it still
  has more than one active child process after 5 seconds.
* tearDownModule() now checks for dangling processes and threads
  before sleep 500 ms. And it now only sleeps if there is a least one
  dangling process or thread.
@vstinner vstinner merged commit ffb4940 into python:master Jul 24, 2017
@vstinner vstinner deleted the reap_children branch July 24, 2017 23:55
vstinner added a commit that referenced this pull request Jul 26, 2017
…r to 3.6 (#2879)

* bpo-26762: Avoid daemon process in _test_multiprocessing (#2842)

test_level() of _test_multiprocessing._TestLogging now uses regular
processes rather than daemon processes to prevent zombi processes
(to not "leak" processes).
(cherry picked from commit 0663495)

* test_multiprocessing: Fix dangling process/thread (#2850)

bpo-26762: Fix more dangling processes and threads in
test_multiprocessing:

* Queue: call close() followed by join_thread()
* Process: call join() or self.addCleanup(p.join)
(cherry picked from commit d7e64d9)

* test_multiprocessing detects dangling per test case (#2841)

bpo-26762: test_multiprocessing now detects dangling processes and
threads per test case classes:

* setUpClass()/tearDownClass() of mixin classes now check if
  multiprocessing.process._dangling or threading._dangling was
  modified to detect "dangling" processses and threads.
* ManagerMixin.tearDownClass() now also emits a warning if it still
  has more than one active child process after 5 seconds.
* tearDownModule() now checks for dangling processes and threads
  before sleep 500 ms. And it now only sleeps if there is a least one
  dangling process or thread.
(cherry picked from commit ffb4940)

* bpo-26762: test_multiprocessing close more queues (#2855)

* Close explicitly queues to make sure that we don't leave dangling
  threads
* test_queue_in_process(): remove unused queue
* test_access() joins also the process to fix a random warning
(cherry picked from commit b4c5296)

* bpo-31019: Fix multiprocessing.Process.is_alive() (#2875)

multiprocessing.Process.is_alive() now removes the process from the
_children set if the process completed.

The change prevents leaking "dangling" processes.
(cherry picked from commit 2db6482)
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.

3 participants