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.

Title: timing test too tight
Type: behavior Stage: resolved
Components: Library (Lib), Tests Versions: Python 3.4
Status: closed Resolution: duplicate
Dependencies: Superseder: test_asyncio: test__run_once timings should be relaxed
View: 19579
Assigned To: Nosy List: ezio.melotti, gvanrossum, pitrou
Priority: normal Keywords:

Created on 2013-10-23 22:20 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (2)
msg201077 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2013-10-23 22:20
Looks like test_asyncio still has rather tight timing expectations:

FAIL: test__run_once (test.test_asyncio.test_base_events.BaseEventLoopTests)
Traceback (most recent call last):
  File "E:\home\cpython\buildslave\x86\3.x.snakebite-win2k8r2sp1-x86\build\lib\test\test_asyncio\", line 182, in test__run_once
    self.assertTrue(9.99 < t < 10.1, t)
AssertionError: False is not true : 9.98499999998603
msg202717 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2013-11-12 20:19
Also this should use assertAlmostEqual().
Date User Action Args
2022-04-11 14:57:52adminsetgithub: 63570
2013-11-17 00:57:58ezio.melottisetstatus: open -> closed
stage: resolved
2013-11-14 02:04:47gvanrossumsetsuperseder: test_asyncio: test__run_once timings should be relaxed
resolution: duplicate
2013-11-14 01:46:03pitrousetnosy: + gvanrossum
2013-11-12 20:19:11ezio.melottisetnosy: + ezio.melotti
messages: + msg202717
2013-10-23 22:20:01pitroucreate