Repository navigation
test_asyncio prints some junk #66184
Description
| BPO | 21985 |
|---|---|
| Nosy | @gvanrossum, @pitrou, @vstinner, @giampaolo, @1st1 |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2014-07-16.16:57:40.462>
created_at = <Date 2014-07-15.23:04:27.231>
labels = ['type-bug', 'tests', 'expert-asyncio']
title = 'test_asyncio prints some junk'
updated_at = <Date 2014-07-16.16:57:40.461>
user = 'https://github.com/pitrou'bugs.python.org fields:
activity = <Date 2014-07-16.16:57:40.461>
actor = 'vstinner'
assignee = 'none'
closed = True
closed_date = <Date 2014-07-16.16:57:40.462>
closer = 'vstinner'
components = ['Tests', 'asyncio']
creation = <Date 2014-07-15.23:04:27.231>
creator = 'pitrou'
dependencies = []
files = []
hgrepos = []
issue_num = 21985
keywords = []
message_count = 4.0
messages = ['223156', '223182', '223183', '223234']
nosy_count = 6.0
nosy_names = ['gvanrossum', 'pitrou', 'vstinner', 'giampaolo.rodola', 'python-dev', 'yselivanov']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue21985'
versions = []
Activity
pitrou commentedon Jul 15, 2014
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
vstinner commentedon Jul 16, 2014
"Task was destroyed but it is pending!" messages come from the issue bpo-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 bpo-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.
python-dev commentedon Jul 16, 2014
New changeset 1ff9ce2204ee by Victor Stinner in branch 'default':
Issue bpo-21645, bpo-21985: Remove debug code
http://hg.python.org/cpython/rev/1ff9ce2204ee
vstinner commentedon Jul 16, 2014
I fixed last warnings in tests ran in debug mode. I close the issue.