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
GitMate.io thinks the contributor most likely able to help you is @asvetlov.
Possibly related issues are #2265 (RuntimeError: set_wakeup_fd only works in main thread), #930 (aiohttp.Timeout causes CancelledError), #841 (CTRL+C to stop doesn't work in python -m aiohttp.web ), #3004 (Ctrl+C not work as excepted for aiohttp on windows), and #3175 (aiohttp client timeout does not work).
Thanks for the report.
xdist creates several threads to execute tested code, aiohttp wants to subscribe on SIGINT and SIGTEM by default even if the thread is not the main.
We can add skipping signals handling if done from subthread (and raise a warning, sure).
But the real problem is: asyncio semi-working when the thread is not the main.
It works perfectly fine in 98% cases but can raise weird results when used for Unix signals or subproceses.
Now I have no clear vision of how to handle it
Long story short
Combining
pytest-aiohttp
andpytest-xdist
an error is triggered sometimes from theloop
fixture.Let me know if you think the issue is more on the pytest(-xdist) side.
Expected behaviour
No error.
Actual behaviour
Steps to reproduce
I've copied the same test file 10 times (just to have some tests to work with).
I use bash in order to run pytest several times until it fails:
Not sure why, but the verbose flag seems to affect it:
-v
Your environment
Tested on 3.6 and 3.7.
8 Cores CPU
The text was updated successfully, but these errors were encountered: