gh-109840: Fix multiprocessing test_waitfor_timeout() (GH-110428)
Don't measure the CI performance: don't fail if cond.wait_for() takes
longer than 1 second on a slow CI.
(cherry picked from commit
5eae8dc2cb832af6ae1ee340fb0194107fe3bd6e)
Co-authored-by: Victor Stinner <vstinner@python.org>
def _test_waitfor_timeout_f(cls, cond, state, success, sem):
sem.release()
with cond:
- expected = 0.1
+ expected = 0.100
dt = time.monotonic()
result = cond.wait_for(lambda : state.value==4, timeout=expected)
dt = time.monotonic() - dt
# borrow logic in assertTimeout() from test/lock_tests.py
- if not result and expected * 0.6 < dt < expected * 10.0:
+ if not result and expected * 0.6 <= dt:
success.value = True
@unittest.skipUnless(HAS_SHAREDCTYPES, 'needs sharedctypes')
# Only increment 3 times, so state == 4 is never reached.
for i in range(3):
- time.sleep(0.01)
+ time.sleep(0.010)
with cond:
state.value += 1
cond.notify()