-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pytest fixture aiohttp_raw_server not cleaning up properly #3570
Comments
GitMate.io thinks the contributor most likely able to help you is @asvetlov. Possibly related issues are #2223 (Pytest: Allow coroutine fixtures), #2578 (Review pytest fixture names), #1425 (Write a doc for pytest fixtures), #2572 (test_client fixture broken with pytest==2.3.3), and #3169 (pytest plugin's async fixtures don’t work with pytest 3.7.0). |
Maybe call |
Sure, this is just meant as a minimal example showing the leaking server socket. (And other random fixtures become cleaner when the port can be known at fixture-generation time) |
Thank you for the report. Sorry, I have a very limited spare time for this weeks. |
Since #3932 was merged and @Dreamsorcerer what do you think? |
I guess if this feature no longer exists, then this is no longer relevant. Feel free to reopen if I'm mistaken. |
Note that it is only removed in aiohttp 4. But, I doubt anyone is going to spend time supporting a deprecated feature in the 3.x releases. |
When using
aiohttp_raw_server
under some circumstances the listening socketis not closed properly during fixture teardown.
E OSError: [Errno 98] Address already in use
Tested inside the current
python:3.6
docker image with the following packages:Pipfile.lock
The text was updated successfully, but these errors were encountered: