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
test_asyncio: test_sock_client_fail() changes asyncio.events._event_loop_policy #90864
Comments
Seen on s390x RHEL7 Refleaks 3.x: == Tests result: FAILURE == ---------------------------------------------------------------------- OK ---------------------------------------------------------------------- OK ---------------------------------------------------------------------- OK ---------------------------------------------------------------------- OK ---------------------------------------------------------------------- OK ---------------------------------------------------------------------- OK |
By default, asyncio.events._event_loop_policy is None: $ ./python -i
>>> import asyncio; asyncio.events._event_loop_policy is None
True After running the test, it changes: vstinner@apu$ ./python -i
Python 3.11.0a5+ (heads/main:46328d8ae6, Feb 9 2022, 21:25:58) [GCC 11.2.1 20211203 (Red Hat 11.2.1-7)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import asyncio; asyncio.events._event_loop_policy is None
True
>>>
vstinner@apu$ ./python -i -m test test_asyncio -m test_sock_client_fail
(...)
Tests result: SUCCESS
(...)
SystemExit: 0
>>> import asyncio; asyncio.events._event_loop_policy
<asyncio.unix_events._UnixDefaultEventLoopPolicy object at 0x7ff7286e7530> |
Thanks for the report! |
With PR 31253 fix, I confirm that it fix my bug explained in msg412992. commit 012e77e
|
Heh, I just ran into this for test_taskgroups as well. (Alas, I had debugged and fixed it independently before I found this. :-) |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: