fix: Don't assume ordering of ThreadPoolExecutor submissions #5052
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.
Proposed Commit Message
Additional Context
We've had some flaky test failures for a bit now: [example]
This test was never guaranteed to succeed, it just apparently did because of cPython ThreadpoolExecutor implementation. Python 3.13 brings lots of threading changes - it is unsurprising that this test now fails occasionally.
Test Steps
It passes for me locally and I don't have a Python 3.13 interpreter locally so... did ci pass?