[issue19371] timing test too tight

2013-11-16 Thread Ezio Melotti
Changes by Ezio Melotti ezio.melo...@gmail.com: -- stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19371 ___

[issue19371] timing test too tight

2013-11-13 Thread Antoine Pitrou
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +gvanrossum ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19371 ___ ___ Python-bugs-list

[issue19371] timing test too tight

2013-11-13 Thread Guido van Rossum
Changes by Guido van Rossum gu...@python.org: -- resolution: - duplicate superseder: - test_asyncio: test__run_once timings should be relaxed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19371

[issue19371] timing test too tight

2013-11-12 Thread Ezio Melotti
Ezio Melotti added the comment: Also this should use assertAlmostEqual(). -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19371 ___

[issue19371] timing test too tight

2013-10-23 Thread Antoine Pitrou
New submission from Antoine Pitrou: Looks like test_asyncio still has rather tight timing expectations: http://buildbot.python.org/all/builders/x86%20Windows%20Server%202008%20%5BSB%5D%203.x/builds/1495/steps/test/logs/stdio