Message340608
The test output from test_sys_settrace makes it look like a couple of the async tracing tests aren't cleaning up after themselves properly:
```
[ncoghlan@localhost cpython]$ ./python -m test test_sys_settrace
Run tests sequentially
0:00:00 load avg: 1.27 [1/1] test_sys_settrace
unhandled exception during asyncio.run() shutdown
task: <Task finished name='Task-8' coro=<<async_generator_athrow without __name__>()> exception=RuntimeError("can't send non-None value to a just-started coroutine")>
RuntimeError: can't send non-None value to a just-started coroutine
unhandled exception during asyncio.run() shutdown
task: <Task finished name='Task-11' coro=<<async_generator_athrow without __name__>()> exception=RuntimeError("can't send non-None value to a just-started coroutine")>
RuntimeError: can't send non-None value to a just-started coroutine
== Tests result: SUCCESS ==
1 test OK.
Total duration: 102 ms
Tests result: SUCCESS
```
If that output is actually expected as part of the test, it would be helpful if the test printed a message beforehand saying to expect it. Otherwise, it would be desirable for the test to clean up after itself and keep the messages from being displayed in the first place. |
|
Date |
User |
Action |
Args |
2019-04-21 13:33:08 | ncoghlan | set | recipients:
+ ncoghlan, asvetlov, yselivanov |
2019-04-21 13:33:08 | ncoghlan | set | messageid: <1555853588.91.0.708286420314.issue36692@roundup.psfhosted.org> |
2019-04-21 13:33:08 | ncoghlan | link | issue36692 messages |
2019-04-21 13:33:08 | ncoghlan | create | |
|