[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

Changes by STINNER Victor : -- resolution: -> fixed stage: -> resolved status: open -> closed versions: +Python 3.5, Python 3.6 ___ Python tracker

[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

STINNER Victor added the comment: New changeset 157b6ad677b7b330d30b2bb5ffbb2edac77b78cb by Victor Stinner in branch '3.5': bpo-30908: Fix dangling thread in test_os.TestSendfile (#2680) (#2845) https://github.com/python/cpython/commit/157b6ad677b7b330d30b2bb5ffbb2edac77b78cb --

[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

STINNER Victor added the comment: New changeset bb33ccfc5a216eff753b10a8dc59ec0277f1e1fb by Victor Stinner in branch '3.6': bpo-30908: Fix dangling thread in test_os.TestSendfile (#2680) (#2844) https://github.com/python/cpython/commit/bb33ccfc5a216eff753b10a8dc59ec0277f1e1fb --

[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

STINNER Victor added the comment: Serhiy Storchaka: If you would like to enhance the unittest module, please open a new issue. I prefer to keep this one for the very specific test_os bug. -- ___ Python tracker

[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

Changes by STINNER Victor : -- pull_requests: +2889 ___ Python tracker ___ ___

[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

Changes by STINNER Victor : -- pull_requests: +2888 ___ Python tracker ___ ___

[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

Serhiy Storchaka added the comment: The alternate solution is to remove all references to test instances before calling tearDownClass(). Interesting, that this warning is occurred only in the leak hunting mode. In normal cases test instances are removed from a testsuite, but regrtest hacks

[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

STINNER Victor added the comment: New changeset d1cc037d1442cc35d1b194ec8e50901514360949 by Victor Stinner in branch 'master': bpo-30908: Fix dangling thread in test_os.TestSendfile (#2680) https://github.com/python/cpython/commit/d1cc037d1442cc35d1b194ec8e50901514360949 --

[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

STINNER Victor added the comment: > This isn't specific to test_keywords. Dangling threads occurred even if > replace the test body with just "return". This is caused by setUp/tearDown or > setUpClass/tearDownClass. Right, see my PR #2680. The general problem is that tearDownClass() seems to

[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

Serhiy Storchaka added the comment: This isn't specific to test_keywords. Dangling threads occurred even if replace the test body with just "return". This is caused by setUp/tearDown or setUpClass/tearDownClass. -- nosy: +serhiy.storchaka ___

[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

Changes by STINNER Victor : -- pull_requests: +2746 ___ Python tracker ___ ___

[issue30908] test_os.TestSendfile.test_keywords() leaks dangling threads

New submission from STINNER Victor: The test_keywords() test of test_os.TestSendfile emits a warning about dangling threads: haypo@selma$ ./python -m test --fail-env-changed -R 3:3 test_os -m test.test_os.TestSendfile.test_keywords Run tests sequentially 0:00:00 load avg: 0.53 [1/1] test_os