[issue5025] test_kqueue failure on OS X

Mark Dickinson added the comment: Fixed in the trunk in r68897. Will merge to 2.6, 3.0 and 3.1. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue5025] test_kqueue failure on OS X

Changes by Mark Dickinson : -- priority: -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue5025] test_kqueue failure on OS X

Mark Dickinson added the comment: I just saw this same test_kqueue failure pop up on the OS X 3.x buildbot, so it's evidently not just a peculiarity of my machine. Unless there are any objections, I'll go ahead and check this in: I think it's a sufficiently trivial fix that it's not worth was

[issue5025] test_kqueue failure on OS X

Mark Dickinson added the comment: Here's a patch: - add a time.sleep(1.0) in between calls to kq.control - restructure for loop slightly: move initial kq.control call inside it - bump number of trials from 5 to 10 (why not?!) - produce more meaningful error message in the unlikely event

[issue5025] test_kqueue failure on OS X

Jean-Paul Calderone added the comment: > My first impression was that the '1' in 'kq.control(None, 4, 1)' already did this; i.e., that it meant that the kq.control function would wait up to 1 second for a response, but that doesn't seem to be true. Since there are events in the result, the cal

[issue5025] test_kqueue failure on OS X

New submission from Mark Dickinson : I just got a one-off, non-reproducible test_kqueue failure, during a 'make test' of the trunk, on OS X 10.5.6. Here's the output: test_kqueue test test_kqueue failed -- Traceback (most recent call last): File "/Users/dickinsm/python_source/trunk/Lib/test/