As a member of the Night's Watch, I'm fixing the CI in the darkness for you (*). Last weeks, I managed to fix most issues. But I decided to give up on test_asyncio failures. I no longer have the bandwidth to investigate these complex issues.
I need your help to debug and fix the following test_asyncio issues.
(1) "test_asyncio altered the execution environment" open for almost one year https://bugs.python.org/issue38912
(2) "asyncio: MultiLoopWatcher has a race condition (test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x)" open for longer than one year https://bugs.python.org/issue38323
There are 8 more open issues which contain "test_asyncio" in their title, but these 2 are the ones causing most troubles on the CI.
Thanks, Justin! I'll look over your PR, try to replicate the failure locally, and test it against the patch to see if it still occurs. I think your analysis of the issue makes sense, with it likely being a race condition between the test prototype "MyProto" and the event loop.
On Thu, Oct 15, 2020 at 5:41 PM firstname.lastname@example.org wrote:
I've submitted a PR for one of the simpler remaining exceptions described in https://bugs.python.org/issue38912: https://github.com/python/cpython/pull/22691 _______________________________________________ Python-Dev mailing list -- email@example.com To unsubscribe send an email to firstname.lastname@example.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://email@example.com/message/M43PXZT3... Code of Conduct: http://python.org/psf/codeofconduct/