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.

Author vstinner
Recipients gvanrossum, neologix, python-dev, vstinner
Date 2014-01-31.16:01:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391184061.71.0.668103832826.issue20452@psf.upfronthosting.co.za>
In-reply-to
Content
There is a similar (but different?) issue on Windows XP. I tried to fix it with the 4 last commits.

The test uses a busy loop. The scheduled handle is called after 0.100 - granularity. The granularity is usually 15.6 ms on Windows, so the expected mimiumum is around 0.084 (not 0.090). Attached patch test_base_events.patch uses the granularity to test the minimum. The check on the maximum should maybe be removed because of our slow buildbots.

http://buildbot.python.org/all/builders/x86%20XP-4%203.x/builds/10071/steps/test/logs/stdio

======================================================================
FAIL: test_time_and_call_at (test.test_asyncio.test_base_events.BaseEventLoopTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "D:\cygwin\home\db3l\buildarea\3.x.bolen-windows\build\lib\test\test_asyncio\test_base_events.py", line 124, in test_time_and_call_at
    self.assertTrue(0.09 <= t1-t0 <= 0.9, t1-t0)
AssertionError: False is not true : 0.08999999985098839
History
Date User Action Args
2014-01-31 16:01:01vstinnersetrecipients: + vstinner, gvanrossum, neologix, python-dev
2014-01-31 16:01:01vstinnersetmessageid: <1391184061.71.0.668103832826.issue20452@psf.upfronthosting.co.za>
2014-01-31 16:01:01vstinnerlinkissue20452 messages
2014-01-31 16:01:01vstinnercreate