Message 300630 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	vstinner
Recipients	vstinner
Date	2017-08-21.15:48:53
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1503330533.41.0.899332710232.issue31247@psf.upfronthosting.co.za>
In-reply-to

Content
Using PR 3138 of bpo-31234, I noticed that test_xmlrpc leaks dangling threads. Example: haypo@selma$ ./python -m test -v test_xmlrpc --fail-env-changed -m test.test_xmlrpc.MultiPathServerTestCase.test_path1 == CPython 3.7.0a0 (heads/master:0267128, Aug 21 2017, 17:23:11) [GCC 6.4.1 20170727 (Red Hat 6.4.1-1)] (...) Warning -- threading_cleanup() detected 0 leaked threads (count: 0, dangling: 2) test_xmlrpc failed (env changed) (...) It seems like xmlrpc error handling creates reference leaks. Attached PR fixes the issue.

Using PR 3138 of bpo-31234, I noticed that test_xmlrpc leaks dangling threads. Example:

haypo@selma$ ./python -m test -v test_xmlrpc --fail-env-changed -m test.test_xmlrpc.MultiPathServerTestCase.test_path1
== CPython 3.7.0a0 (heads/master:0267128, Aug 21 2017, 17:23:11) [GCC 6.4.1 20170727 (Red Hat 6.4.1-1)]
(...)
Warning -- threading_cleanup() detected 0 leaked threads (count: 0, dangling: 2)
test_xmlrpc failed (env changed)
(...)

It seems like xmlrpc error handling creates reference leaks. Attached PR fixes the issue.

History
Date	User	Action	Args
2017-08-21 15:48:53	vstinner	set	recipients: + vstinner
2017-08-21 15:48:53	vstinner	set	messageid: <1503330533.41.0.899332710232.issue31247@psf.upfronthosting.co.za>
2017-08-21 15:48:53	vstinner	link	issue31247 messages
2017-08-21 15:48:53	vstinner	create