gh-109565: Fix concurrent.futures test_future_times_out()#109949
gh-109565: Fix concurrent.futures test_future_times_out()#109949vstinner merged 1 commit intopython:mainfrom
Conversation
as_completed() uses a timeout of 100 ms instead of 10 ms. Windows monotonic clock resolution is around 15.6 ms.
bf4ab70 to
afcaa29
Compare
|
Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
|
Sorry, @vstinner, I could not cleanly backport this to |
…onGH-109949) as_completed() uses a timeout of 100 ms instead of 10 ms. Windows monotonic clock resolution is around 15.6 ms. (cherry picked from commit b1aebf1) Co-authored-by: Victor Stinner <vstinner@python.org>
|
GH-109952 is a backport of this pull request to the 3.12 branch. |
|
|
Python 3.11 is not affected. In Python 3.11, the test is called |
…on#109949) as_completed() uses a timeout of 100 ms instead of 10 ms. Windows monotonic clock resolution is around 15.6 ms.
…on#109949) as_completed() uses a timeout of 100 ms instead of 10 ms. Windows monotonic clock resolution is around 15.6 ms.
as_completed() uses a timeout of 100 ms instead of 10 ms. Windows monotonic clock resolution is around 15.6 ms.