Guido van Rossum added the comment:
No time for a full review yet, but a comment on the timeout test failure you
are observing in Tulip. This particular test schedules a task that sleeps for
20 msecs, and first calls run_until_complete() with a timeout of 10 msecs, and
then calls it again without a timeout. It checks that the first call takes
approximately 10 msec and the second call too. But for some reason it is okay
if the first call takes quite a bit longer (up to 18 msec) and then the second
check is wrong.
Can you try again with the failing assert replaced with this?
self.assertTrue(0.018 <= t2-t0 <= 0.028, t2-t0)
That should be a better way to check that code works.
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue16853>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
