New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sporadic test_asyncio failure under FreeBSD #63504
Comments
====================================================================== Traceback (most recent call last):
File "/usr/home/buildbot/koobs-freebsd10/3.x.koobs-freebsd10/build/Lib/test/test_asyncio/test_events.py", line 568, in test_create_server
self.assertEqual(3, proto.nbytes)
AssertionError: 3 != 0 |
I'm guessing there's a whole lot of tests calling run_briefly() that really need to be fixed along these lines: http://code.google.com/p/tulip/source/detail?r=44e4c8257a9d I'd like to add a new method to test_utils.py for that purpose. But if at all possible I'd like to do that post alpha release. |
How about the following? |
That patch looks good except please don't call it wait_for(), since there's already tasks.wait_for(). You can call it run_until(). Having to pass the loop to sleep() is only really required in the tests -- there was a movement a while ago (started by Alex Gaynor and supported by Glyph) to always pass in an explicit loop; my compromise was to force the tests to always pass in a loop (by using set_event_loop(None)). |
New changeset f1447c152fb7 by Antoine Pitrou in branch 'default': |
Ok, I called it run_until. Hopefully this will manage to appease the buildbot. |
Looks ok on the buildbot. |
You rock Antoine. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: