You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test_handle_called_with_mp_queue() of test_logging: threading_cleanup() failed to cleanup, on AMD64 FreeBSD 10.x Shared 3.x #75224
(...)
test_output (test.test_logging.UnixSocketHandlerTest) ... ok
test_output (test.test_logging.UnixDatagramHandlerTest) ... ok
test_output (test.test_logging.UnixSysLogHandlerTest) ... ok
test__all__ (test.test_logging.MiscTestCase) ... ok
test_handle_called_with_mp_queue (test.test_logging.QueueListenerTest) ... Warning -- threading_cleanup() failed to cleanup -1 threads after 4 sec (count: 0, dangling: 1)
ok
test_handle_called_with_queue_queue (test.test_logging.QueueListenerTest) ... ok
test_no_messages_in_queue_after_stop (test.test_logging.QueueListenerTest) ... ok
(...)
See also bpo-30830: "HTTPHandlerTest of test_logging leaks a "dangling" thread on AMD64 FreeBSD CURRENT Non-Debug 3.x".
changed the title [-]test_handle_called_with_mp_queue() of test_logging: threading_cleanup() failed to cleanup[/-][+]test_handle_called_with_mp_queue() of test_logging: threading_cleanup() failed to cleanup, on AMD64 FreeBSD 10.x Shared 3.x[/+]on Jul 26, 2017
I ran "./python -m test -v test_logging --fail-env-changed -F" in 3 terminals on the FreeBSD 10 buildbot, and I failed to reproduce the bug. I ran my test for 5 minutes.
Maybe threading_cleanup() should call support.gc_collect().
Activity
vstinner commentedon Jul 26, 2017
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%2010.x%20Shared%203.x/builds/625/steps/test/logs/stdio
(...)
test_output (test.test_logging.UnixSocketHandlerTest) ... ok
test_output (test.test_logging.UnixDatagramHandlerTest) ... ok
test_output (test.test_logging.UnixSysLogHandlerTest) ... ok
test__all__ (test.test_logging.MiscTestCase) ... ok
test_handle_called_with_mp_queue (test.test_logging.QueueListenerTest) ... Warning -- threading_cleanup() failed to cleanup -1 threads after 4 sec (count: 0, dangling: 1)
ok
test_handle_called_with_queue_queue (test.test_logging.QueueListenerTest) ... ok
test_no_messages_in_queue_after_stop (test.test_logging.QueueListenerTest) ... ok
(...)
See also bpo-30830: "HTTPHandlerTest of test_logging leaks a "dangling" thread on AMD64 FreeBSD CURRENT Non-Debug 3.x".
Previously fixed warnings: bpo-30131.
[-]test_handle_called_with_mp_queue() of test_logging: threading_cleanup() failed to cleanup[/-][+]test_handle_called_with_mp_queue() of test_logging: threading_cleanup() failed to cleanup, on AMD64 FreeBSD 10.x Shared 3.x[/+]vstinner commentedon Jul 28, 2017
I ran "./python -m test -v test_logging --fail-env-changed -F" in 3 terminals on the FreeBSD 10 buildbot, and I failed to reproduce the bug. I ran my test for 5 minutes.
Maybe threading_cleanup() should call support.gc_collect().
vstinner commentedon Aug 9, 2017
New fail:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%2010.x%20Shared%203.x/builds/680/steps/test/logs/stdio
test_handle_called_with_mp_queue (test.test_logging.QueueListenerTest) ... Warning -- threading_cleanup() failed to cleanup -1 threads after 3 sec (count: 0, dangling: 1)
ok
vstinner commentedon Aug 10, 2017
Let's mark this issue as a duplicate of bpo-30830.