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.

Author martin.panter
Recipients gvanrossum, martin.panter, vstinner, yselivanov
Date 2015-10-01.00:40:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1443660054.48.0.940561400662.issue25272@psf.upfronthosting.co.za>
In-reply-to
Content
Another source of noise is this warning about a task being slow to respond. I briefly investigated this a while back. I concluded that it only happens when other tests are run before it; it does not happen when test_asyncio is run alone. It is caused by the garbage collector, because I was able to stop it by invoking gc.collect() at a particular point in the test.

$ make -s -j2 && LC_TIME= ./python -bWall -m test -j0
[. . .]
[ 36/399] test_bytes
[ 37/399] test_bz2 -- running: test_buffer (32 sec), test_asyncore (42 sec), test_asyncio (44 sec)
[ 38/399] test_buffer (33 sec) -- running: test_asyncore (43 sec), test_asyncio (45 sec)
[ 39/399] test_asyncio (44 sec) -- running: test_asyncore (43 sec)
Executing <Task finished coro=<CoroutineTests.test_async_def_wrapped.<locals>.start() done, defined at /media/disk/home/proj/python/cpython/Lib/test/test_asyncio/test_pep492.py:146> result=None created at /media/disk/home/proj/python/cpython/Lib/asyncio/base_events.py:323> took 0.177 seconds
returning true from eof_received() has no effect when using ssl
returning true from eof_received() has no effect when using ssl
History
Date User Action Args
2015-10-01 00:40:54martin.pantersetrecipients: + martin.panter, gvanrossum, vstinner, yselivanov
2015-10-01 00:40:54martin.pantersetmessageid: <1443660054.48.0.940561400662.issue25272@psf.upfronthosting.co.za>
2015-10-01 00:40:54martin.panterlinkissue25272 messages
2015-10-01 00:40:52martin.pantercreate