Karthikeyan Singaravelan <tir.kar...@gmail.com> added the comment:

This commit seems to generate some warnings in the nested run_until_complete 
test. The check for running loop is now done at run_until_complete itself 
before going through the below code in it to create a future and raised a 
RuntimeError by run_forever as the test used to do. Not sure why CI doesn't 
have these warnings.

PYTHONWARNINGS=always ./python.exe -m test test_asyncio -m 
test_run_until_complete_nesting
0:00:00 load avg: 2.16 Run tests sequentially
0:00:00 load avg: 2.16 [1/1] test_asyncio
/Users/kasingar/stuff/python/cpython/Lib/traceback.py:220: RuntimeWarning: 
coroutine 'EventLoopTestsMixin.test_run_until_complete_nesting.<locals>.coro1' 
was never awaited
  tb.tb_frame.clear()
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
/Users/kasingar/stuff/python/cpython/Lib/traceback.py:220: RuntimeWarning: 
coroutine 'EventLoopTestsMixin.test_run_until_complete_nesting.<locals>.coro1' 
was never awaited
  tb.tb_frame.clear()
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
/Users/kasingar/stuff/python/cpython/Lib/traceback.py:220: RuntimeWarning: 
coroutine 'EventLoopTestsMixin.test_run_until_complete_nesting.<locals>.coro1' 
was never awaited
  tb.tb_frame.clear()
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

== Tests result: SUCCESS ==

1 test OK.

Total duration: 164 ms
Tests result: SUCCESS

----------
nosy: +xtreak

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue39191>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to