You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! There is a problem with Python 3.8 cause TimeoutError is not in asyncio.futures anymore, I suppose, but in asyncio itself already. The exception occurs in arsenic.subprocess.AsyncioSubprocessImpl.stop_process().
I don't know why but chromedriver is not being terminated but become defunct (zombie) and stay. Arsenic waits for it to terminate for 1 second and kill it but fails with AttributeError because of the fact I stated above.
UPD: if I replace asyncio.futures.TimeoutError to asyncio.TimeoutError I still got problem but in this case the exception is 'the event loop is closed' (in aiohttp.test_utils.setup_test_loop()). By the way something does not let chromedriver to terminate and arsenic event can not kill it - I see the warning in the logs.
Funny fact: when I got 2 tests in my test case everything seems fine but if I got more that 2 test in my test case then I face the problem.
It seems that problems began when I migrated from aiohttp 2.3.5 to 3.6.2 I use pytest and unittest.
I will provide an example of my code a little bit later.
UPD: if have figured out that the problem is in aiohttp.test_utils.setup_test_loop(). I have replaced that function from aiohttp 3.6.2 with the one from aiohttp 3.2.5 and the problem is gone.
The text was updated successfully, but these errors were encountered:
konstunn
changed the title
Unable to stop chrome driver process
AioHTTP versions compatibility (sometimes unable to stop chrome driver process)
Dec 16, 2020
Hi! There is a problem with Python 3.8 cause TimeoutError is not in asyncio.futures anymore, I suppose, but in asyncio itself already. The exception occurs in arsenic.subprocess.AsyncioSubprocessImpl.stop_process().
I don't know why but chromedriver is not being terminated but become defunct (zombie) and stay. Arsenic waits for it to terminate for 1 second and kill it but fails with AttributeError because of the fact I stated above.
UPD: if I replace asyncio.futures.TimeoutError to asyncio.TimeoutError I still got problem but in this case the exception is 'the event loop is closed' (in aiohttp.test_utils.setup_test_loop()). By the way something does not let chromedriver to terminate and arsenic event can not kill it - I see the warning in the logs.
Funny fact: when I got 2 tests in my test case everything seems fine but if I got more that 2 test in my test case then I face the problem.
It seems that problems began when I migrated from aiohttp 2.3.5 to 3.6.2 I use pytest and unittest.
I will provide an example of my code a little bit later.
UPD: if have figured out that the problem is in aiohttp.test_utils.setup_test_loop(). I have replaced that function from aiohttp 3.6.2 with the one from aiohttp 3.2.5 and the problem is gone.
The text was updated successfully, but these errors were encountered: