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.

classification
Title: test_asyncio prints some junk
Type: behavior Stage:
Components: asyncio, Tests Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: giampaolo.rodola, gvanrossum, pitrou, python-dev, vstinner, yselivanov
Priority: normal Keywords:

Created on 2014-07-15 23:04 by pitrou, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (4)
msg223156 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2014-07-15 23:04
It could be nice if it could stay silent (at least in non-verbose mode).

[ 24/390] test_asyncio
Task was destroyed but it is pending!
task: <Task pending coro=<CoroutineGatherTests.wrap_futures.<locals>.coro() running at /home/antoine/cpython/default/Lib/test/test_asyncio/test_tasks.py:1862> cb=[gather.<locals>._done_callback(2)() at /home/antoine/cpython/default/Lib/asyncio/tasks.py:577] wait_for=<Future finished result=3>>
Task was destroyed but it is pending!
task: <Task pending coro=<CoroutineGatherTests.wrap_futures.<locals>.coro() running at /home/antoine/cpython/default/Lib/test/test_asyncio/test_tasks.py:1862> cb=[gather.<locals>._done_callback(3)() at /home/antoine/cpython/default/Lib/asyncio/tasks.py:577] wait_for=<Future cancelled>>
Task was destroyed but it is pending!
task: <Task pending coro=<CoroutineGatherTests.wrap_futures.<locals>.coro() running at /home/antoine/cpython/default/Lib/test/test_asyncio/test_tasks.py:1862> cb=[gather.<locals>._done_callback(4)() at /home/antoine/cpython/default/Lib/asyncio/tasks.py:577] wait_for=<Future finished exception=RuntimeError()>>
Task was destroyed but it is pending!
task: <Task pending coro=<sleep() done, defined at /home/antoine/cpython/default/Lib/asyncio/tasks.py:489> wait_for=<Future pending cb=[Task._wakeup()]>>
Read pipe 9 connected: (<_UnixReadPipeTransport fd=9 polling>, <asyncio.streams.StreamReaderProtocol object at 0x7f2c0b358dc0>)
execute program '/home/antoine/cpython/default/python'
process '/home/antoine/cpython/default/python' created: pid 4233
execute program '/home/antoine/cpython/default/python': <_UnixSubprocessTransport pid=4233>
poll took 36.605 ms: 1 events
poll took 6.615 ms: 0 events
process 4233 exited with returncode 0
<_UnixSubprocessTransport pid=4233> exited with return code 0
poll took 0.032 ms: 1 events
<_UnixReadPipeTransport fd=9 polling> was closed by peer
msg223182 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-07-16 08:24
"Task was destroyed but it is pending!" messages come from the issue #21163, I know that I have to make these messages quiet and I don't know yet how to fix this.

"Read pipe 9 connected: ... <until the end>" output was specific to the issue #21645. I created a dedicated repository to investigate this issue. It looks like a severe race condition in signal handling when there are more than 1 thread on FreeBSD.
msg223183 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2014-07-16 08:24
New changeset 1ff9ce2204ee by Victor Stinner in branch 'default':
Issue #21645, #21985: Remove debug code
http://hg.python.org/cpython/rev/1ff9ce2204ee
msg223234 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-07-16 16:57
I fixed last warnings in tests ran in debug mode. I close the issue.
History
Date User Action Args
2022-04-11 14:58:05adminsetgithub: 66184
2014-07-16 16:57:40vstinnersetstatus: open -> closed
resolution: fixed
messages: + msg223234
2014-07-16 08:25:41vstinnersetcomponents: + asyncio
2014-07-16 08:24:46python-devsetnosy: + python-dev
messages: + msg223183
2014-07-16 08:24:03vstinnersetmessages: + msg223182
2014-07-15 23:04:27pitroucreate