gh-95736: Fix event loop creation in IsolatedAsyncioTestCase#96033
Conversation
It should be created before calling the setUp() method, but after checking for skipping a test.
|
🤖 New build scheduled with the buildbot fleet by @serhiy-storchaka for commit 1194f25 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
|
I have a new ticket and PR GH-96031 |
|
Well, this fix sure looks simpler than @tiran's. I'll defer judgment until I've had time to look at things more thoroughly though. |
|
Let's merge this PR to unblock and fix main branch. We can solve #95736 and correct the problematic implementation in the async unittest helper later. |
|
The wasm32-wasi PR build fails with a different error: |
|
Tho other WASM builds are fine. @tiran what do you think? |
gvanrossum
left a comment
There was a problem hiding this comment.
Assuming the failing buildbots are explained this LGTM.
It's an unrelated error which is already fixed in main. |
|
@serhiy-storchaka: Status check is done, and it's a pending ❌ . |
1 similar comment
|
@serhiy-storchaka: Status check is done, and it's a pending ❌ . |
|
Status check is done, and it's a success ✅ . |
|
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
|
Sorry @serhiy-storchaka, I had trouble checking out the |
|
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11. |
|
GH-96041 is a backport of this pull request to the 3.11 branch. |
…ythonGH-96033) It should be created before calling the setUp() method, but after checking for skipping a test. Automerge-Triggered-By: GH:tiran (cherry picked from commit 3651710) Co-authored-by: Serhiy Storchaka <[email protected]>
It should be created before calling the setUp() method, but after
checking for skipping a test.
IsolatedAsyncioTestCasedoes not callasyncio.set_event_loopbeforesetUpanymore,asyncio.Runner+PidFdChildWatcherleaves zombie processes #95736Automerge-Triggered-By: GH:tiran