-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
GH-95736: fix IsolatedAsyncioTestCase to set event loop before calling setup functions #95898
Conversation
This is waiting for a resolution of #95900 (comment). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay this is what I had in mind so LGTM from that perspective, but we need to get a better understanding of what Thomas is asking about the event loop policy.
So we've established that in tests deriving from It makes me wonder if the @kumaraditya303 Can you shorten the test per my remarks previously in this issue? I'd also like to invite @serhiy-storchaka to review this, since he did some work on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general the solution LGTM, but I have a lot of questions about testing code.
Done, FTR the previous test was mostly copied from #95736 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Thanks @kumaraditya303 for the PR, and @gvanrossum for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11. |
…re calling setup functions (pythonGH-95898) (cherry picked from commit 9d51599) Co-authored-by: Kumar Aditya <[email protected]>
GH-96027 is a backport of this pull request to the 3.11 branch. |
|
|
|
Urm, the WebAssembly buildbot failures are actually due to our test. We need to fix this before we can backport. Apparently by forcing a call to |
Rest of the discussion in the corresponding issue, starting at #95736 (comment) |
…er before calling setup functions (pythonGH-95898) (cherry picked from commit 9d51599) Co-authored-by: Kumar Aditya <[email protected]>
…er before calling setup functions (pythonGH-95898) (cherry picked from commit 9d51599) Co-authored-by: Kumar Aditya <[email protected]> Co-authored-by: Serhiy Storchaka [email protected]
…er before calling setup functions (pythonGH-95898) (cherry picked from commit 9d51599) Co-authored-by: Kumar Aditya <[email protected]> Co-authored-by: Serhiy Storchaka [email protected]
…er before calling setup functions (pythonGH-95898) (cherry picked from commit 9d51599) Co-authored-by: Kumar Aditya <[email protected]> Co-authored-by: Serhiy Storchaka <[email protected]>
…er before calling setup functions (pythonGH-95898) (cherry picked from commit 9d51599) Co-authored-by: Kumar Aditya <[email protected]> Co-authored-by: Serhiy Storchaka <[email protected]>
IsolatedAsyncioTestCase
does not callasyncio.set_event_loop
beforesetUp
anymore,asyncio.Runner
+PidFdChildWatcher
leaves zombie processes #95736