-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Add automatically a SafeChildWatcher to the test loop #2075
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2075 +/- ##
==========================================
- Coverage 97.08% 97.07% -0.02%
==========================================
Files 38 38
Lines 7689 7695 +6
Branches 1344 1345 +1
==========================================
+ Hits 7465 7470 +5
Misses 102 102
- Partials 122 123 +1
Continue to review full report at Codecov.
|
@asvetlov ready for your review |
tests/test_loop.py
Outdated
|
||
@asyncio.coroutine | ||
def test_subprocess_co(loop): | ||
skip_if_on_windows() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please replace it with @pytest.skipif
decorator.
I pretty sure keeping a check alongside with test improves readability.
The fact that on Unix system we don't create automatically a child watcher makes all call to asyncio.create_subprocess_* to fail.
78b503e
to
78bac63
Compare
@asvetlov this is ready for your review |
Cool! |
The fact that on Unix system we don't create automatically a child
watcher makes all call to asyncio.create_subprocess_* to fail.
What do these changes do?
It adds a default child watcher to the test loop.
Are there changes in behavior for the user?
Any
asyncio.create_subprocess_*
call in the application or during a test will work because the ChildWatcher exist (on Unix).No change for Windows.
Related issue number
#2058 #2059
Checklist
CONTRIBUTORS.txt
changes
folder<issue_id>.<type>
for example (588.bug)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.