-
-
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
Failing test in Python 3.8 #3606
Comments
GitMate.io thinks the contributor most likely able to help you is @asvetlov. Possibly related issues are #537 (Drop python 3.3 support), #3458 (Beta release is failed on Python 3.7 bot for Linux), #467 (Failed building wheel for aiohttp on Python 3.5.0rc1), #1302 (Make test suite passed on python 3.6 and default), and #2148 (Failed tests). |
🤔 Should I opened this in https://github.com/aio-libs/pytest-aiohttp instead? |
Nope, here is fine. That repo is just a wrapper to auto-add fixtures. The real code of those is here. |
From prompt look it seems like server isn't listening to port while client sends a request there... |
Same code works in Python 3.7 though. Would this be a regression from Python side or aiohttp? |
I believe it might be an asyncio regression. Our nightly job is failing but for another reason: https://travis-ci.com/aio-libs/aiohttp/jobs/177507070. Let's wait till Andrew takes a look. |
Update: flake8 issue is gone, but the real tests started failing and they get completely stuck at some point. Ref: https://travis-ci.com/aio-libs/aiohttp/jobs/177768192#L764 |
I ran into the same error with the following build: Python 3.8.0a2+ (heads/master:f45813d, Mar 12 2019, 21:49:03). |
Same here with 3.8.0a2. When running the examples from aiohttp I see on netstat that the port is indeed listening but refuses connections. However other stuff I have using asyncio works fine (for example, lx200/examples/tcpserver.py ) |
deep diving into the output with PYTHONASYNCIODEBUG=1, the minimal example produce:
Which seems totally related to #3644. |
Fixed by #3727 |
Nice. Thanks! |
Long story short
I'm seeing tests related to aiohttp that fail in Python 3.8+, but pass in Python 3.7.2.
I encountered this in bedevere, you can check the travis CI log in there. (python/bedevere#154)
Expected behaviour
Tests should be passing.
Actual behaviour
The tests pass for Python 3.7.2, but fail for Python 3.8
Steps to reproduce
I created the following test case: (copy pasted from the docs: https://docs.aiohttp.org/en/stable/testing.html#pytest)
Your environment
Mac OS Mojave 10.14.3 Python 3.8.0a1.
The text was updated successfully, but these errors were encountered: