This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kevinconway
Recipients gvanrossum, kevinconway, vstinner, yselivanov
Date 2016-08-31.03:07:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472612851.68.0.196801920926.issue27906@psf.upfronthosting.co.za>
In-reply-to
Content
I'll dig into the existing asyncio unit tests and see what I can come up with. I'm not sure, yet, exactly what I might test for.

The variables involved with reproducing the error are mostly environmental. CPU speed of the host, amount of CPU bound work happening in handler coroutines, and the rate of new connections are the major contributors we've identified. I'm not sure how I might simulate those in a unit test.

Would it be sufficient to add a test that ensures the _accept_connection calls .accept() on the listening socket 'backlog' number of times in event there are no OS errors?
History
Date User Action Args
2016-08-31 03:07:31kevinconwaysetrecipients: + kevinconway, gvanrossum, vstinner, yselivanov
2016-08-31 03:07:31kevinconwaysetmessageid: <1472612851.68.0.196801920926.issue27906@psf.upfronthosting.co.za>
2016-08-31 03:07:31kevinconwaylinkissue27906 messages
2016-08-31 03:07:31kevinconwaycreate