stdio endpoint tests leave a dirty reactor
|Reported by:||ashfall||Owned by:||glyph|
(github, coverage, patch, buildbot, log)
Description (last modified by glyph)
The problem with many of the tests in StandardIOEndpointsTestCase is that they're using a real reactor, but not actually waiting for the disconnection notification.
It would be nice to avoid using a real reactor (or, for that matter, real stdio streams) in most of these tests; if we want an integration test it should probably live in an isolated subprocess.
Change History (7)
comment:2 Changed 2 years ago by glyph
- Description modified (diff)
- Summary changed from Fix the dirty reactor warnings when tests for the stdio endpoints are run on Windows to stdio endpoint tests leave a dirty reactor
comment:5 follow-up: ↓ 6 Changed 2 years ago by adiroiban
- Keywords review removed
- Owner set to glyph