[issue25272] asyncio tests are getting noisy

Yury Selivanov added the comment: I think I've fixed all of these: https://github.com/python/asyncio/commit/cd4fdbb9ccd7c41a4e7c6b416bb2481ab0e21e1c https://github.com/python/asyncio/commit/1365ac3a37836c6ec50138df8d64a87cdd0ac494 https://github.com/python/asyncio/commit/ae30b2b4244f1526d422500a

[issue25272] asyncio tests are getting noisy

Martin Panter added the comment: New messages seen in Issue 25693 and Issue 25748: /tmp/cpython/Lib/threading.py:864: ResourceWarning: unclosed self._target(*self._args, **self._kwargs) . . . /tmp/cpython/Lib/asyncio/base_events.py:379: ResourceWarning: unclosed event loop <_UnixSelectorEven

[issue25272] asyncio tests are getting noisy

Guido van Rossum added the comment: Or call gc.collect() in that TestCase.setUp()? -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue25272] asyncio tests are getting noisy

STINNER Victor added the comment: > Executing coro=.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 This one is triv

[issue25272] asyncio tests are getting noisy

Martin Panter added the comment: 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 gar

[issue25272] asyncio tests are getting noisy

New submission from Guido van Rossum: In 3.5 and up the asyncio test are pretty chatty with warnings. E.g. a recent run gave me this in 3.5: ./python.exe -m test.test_asyncio .../Users/guido/