➜
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.
Created on 2019-10-24 09:14 by vstinner, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg355308 - (view) | Author: STINNER Victor (vstinner) *  |
Date: 2019-10-24 09:14 | |
On AMD64 FreeBSD Shared 3.8 which is know to be very slow, different test_concurrent_futures tests failed. https://buildbot.python.org/all/#builders/374/builds/3 test_concurrent_futures was run twice. Once in parallel of other tests, then alone in sequence. The first run emitted two "threading_cleanup() failed" warnings and test_idle_thread_reuse() failed: test_idle_thread_reuse (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 1.05s Warning -- threading_cleanup() failed to cleanup 2 threads (count: 2, dangling: 3) test_map (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 3.80s Warning -- threading_cleanup() failed to cleanup -2 threads (count: 0, dangling: 1) FAIL: test_idle_thread_reuse (test.test_concurrent_futures.ThreadPoolExecutorTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/home/buildbot/python/3.8.koobs-freebsd-564d/build/Lib/test/test_concurrent_futures.py", line 782, in test_idle_thread_reuse self.assertEqual(len(executor._threads), 1) AssertionError: 2 != 1 At the second run, test_free_reference() failed: 1:15:08 load avg: 9.24 Re-running test_concurrent_futures in verbose mode FAIL: test_free_reference (test.test_concurrent_futures.ThreadPoolExecutorTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/home/buildbot/python/3.8.koobs-freebsd-564d/build/Lib/test/test_concurrent_futures.py", line 745, in test_free_reference self.assertIsNone(wr()) AssertionError: <test.test_concurrent_futures.MyObject object at 0x8031cc780> is not None |
|||
| msg355309 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2019-10-24 09:15 | |
Logs around the first failure: ... test_zero_timeout (test.test_concurrent_futures.ThreadPoolAsCompletedTest) ... 2.24s ok test_default_workers (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 0.96s ok test_free_reference (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 0.56s ok test_idle_thread_reuse (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 1.05s Warning -- threading_cleanup() failed to cleanup 2 threads (count: 2, dangling: 3) Dangling thread: <Thread(ThreadPoolExecutor-9_1, started daemon 34379716096)> Dangling thread: <_MainThread(MainThread, started 34371022848)> Dangling thread: <Thread(ThreadPoolExecutor-9_0, started daemon 34399619584)> FAIL test_map (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 3.80s Warning -- threading_cleanup() failed to cleanup -2 threads (count: 0, dangling: 1) Dangling thread: <_MainThread(MainThread, started 34371022848)> ok test_map_exception (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 1.67s ok test_map_submits_without_iteration (test.test_concurrent_futures.ThreadPoolExecutorTest) Tests verifying issue 11777. ... 2.64s ok ... |
|||
| msg361588 - (view) | Author: STINNER Victor (vstinner) * |
Date: 2020-02-07 10:58 | |
I didn't see this issue recently, I close the issue. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:22 | admin | set | github: 82759 |
| 2020-02-07 10:58:56 | vstinner | set | status: open -> closed resolution: out of date messages: + msg361588 stage: resolved |
| 2019-10-24 09:15:57 | vstinner | set | messages: + msg355309 |
| 2019-10-24 09:14:34 | vstinner | create | |