Skip to content
This repository has been archived by the owner on Nov 23, 2017. It is now read-only.

Some unit tests are flaky #75

Closed
GoogleCodeExporter opened this issue Apr 10, 2015 · 2 comments
Closed

Some unit tests are flaky #75

GoogleCodeExporter opened this issue Apr 10, 2015 · 2 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

Some unit tests require things to happen within a tight deadline. But buildbots 
are often slow and then these tests become flaky.

Similar for tests that expect data to travel between threads in one event loop 
tick.

See e.g. http://bugs.python.org/msg200231

Original issue reported on code.google.com by gvanrossum@gmail.com on 18 Oct 2013 at 3:01
@GoogleCodeExporter
Copy link
Author 

Another tight deadline candidate if you haven't already picked it up:

======================================================================
FAIL: test_run_until_complete 
(test.test_asyncio.test_events.KqueueEventLoopTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd9/build/Lib/test/test_asyncio/test_events.py", line 218, in test_run_until_complete
    self.assertTrue(0.08 <= t1-t0 <= 0.12, t1-t0)
AssertionError: False is not true : 0.12018337799236178

Original comment by koobs.fr...@gmail.com on 18 Oct 2013 at 9:32

@GoogleCodeExporter
Copy link
Author 

Fixed all that were reported.

Original comment by gvanrossum@gmail.com on 18 Oct 2013 at 10:23

  • Changed state: Fixed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter