homepage

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 serhiy.storchaka
Recipients serhiy.storchaka
Date 2021年09月15日.17:30:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1631727017.23.0.70122988847.issue45212@roundup.psfhosted.org>
In-reply-to
Content
Dangling threads are reported when run test_socket tests which raise SkipTest in setUp() in refleak mode.
$ ./python -m test -R 3:3 test_socket -m testBCM
0:00:00 load avg: 2.53 Run tests sequentially
0:00:00 load avg: 2.53 [1/1] test_socket
beginning 6 repetitions
123456
.Warning -- threading_cleanup() failed to cleanup 1 threads (count: 1, dangling: 1)
Warning -- Dangling thread: <_MainThread(MainThread, started 139675429708416)>
.Warning -- threading_cleanup() failed to cleanup 1 threads (count: 1, dangling: 1)
Warning -- Dangling thread: <_MainThread(MainThread, started 139675429708416)>
.Warning -- threading_cleanup() failed to cleanup 1 threads (count: 1, dangling: 1)
Warning -- Dangling thread: <_MainThread(MainThread, started 139675429708416)>
...
test_socket failed (env changed)
== Tests result: SUCCESS ==
1 test altered the execution environment:
 test_socket
Total duration: 655 ms
Tests result: SUCCESS
It happens because tearDown() is not called if setUp() raises any exception (including SkipTest). If we want to execute some cleanup code it should be registered with addCleanup().
History
Date User Action Args
2021年09月15日 17:30:17serhiy.storchakasetrecipients: + serhiy.storchaka
2021年09月15日 17:30:17serhiy.storchakasetmessageid: <1631727017.23.0.70122988847.issue45212@roundup.psfhosted.org>
2021年09月15日 17:30:17serhiy.storchakalinkissue45212 messages
2021年09月15日 17:30:17serhiy.storchakacreate

AltStyle によって変換されたページ (->オリジナル) /