[ci/cd] fix python tests with more strict scoping#494
Merged
luoyuxia merged 2 commits intoApr 17, 2026
Conversation
Member
Author
|
@luoyuxia @leekeiabstraction I might need some help with verification and running CI/CD a couple of times |
Contributor
I'm always online in the next few hours. |
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
resolves #492
Needs verification(probably a couple of CI/CD runs):
Python CI tests (especially on 3.11) intermittently hang and get killed by the 30s pytest-timeout. The hangs started after the async for loop support was added (#438), which introduced future_into_py-based polling tasks on the shared tokio runtime.
With session-scoped event loops, all tests within a worker share one event loop. Abandoned async generators from earlier tests (e.g., async for ... break) can leave in-flight future_into_py tasks that interact with subsequent tests via the shared event loop.
Per-function scope eliminates cross-test interference.