bpo-16968: Clean up test_concurrent_futures#8099
Conversation
The old test_main function would cause any dangling threads or processes to be reaped silently rather than allowing regrtest to detect and warn about them. Since the shutdown methods of the module should do all of the cleanup for us, we want to get those warnings if they don't.
This allows a change in `support.environment_altered` by `support.reap_children` to be recorded by `saved_test_environment.__exit__`.
|
When you're done making the requested changes, leave the comment: And if you don't make the requested changes, you will be poked with soft cushions! |
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
Maybe just revert Lib/test/libregrtest/runtest.py change? If my runtest.py comment is wrong, I would prefer to see the change as a different PR.
Sorry, something went wrong.
Sorry, something went wrong.
|
@csabella Thanks for the ping. I did, but haven't had the time to swap this back in to think it through :) This PR can be freely rejected or taken over if anyone is sufficiently confident in their understanding of what's going on here; otherwise I'll get back to it one of these years :) |
Sorry, something went wrong.
Ok. I close your PR. |
Sorry, something went wrong.
The old test_main function would cause any dangling threads or processes
to be reaped silently rather than allowing regrtest to detect and warn
about them. Since the shutdown methods of the module should do all of
the cleanup for us, we want to get those warnings if they don't.
https://bugs.python.org/issue16968