-
-
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
Consistent test failures in test test_asyncio.test_streams.test_drain_raises on Windows #98703
Comments
@pablogsal sorry to bother you right after the monumental 3.11 release (thanks for that by the way!). However, I'm setting this as release blocker as it's causing the Windows Buildbots to occasionally fail https://buildbot.python.org/all/#/builders/146. I have already created a PR to fix this. |
Thanks a lot @Fidget-Spinner 🙏 |
Does it needs to be a release blocker? Or just be backported? |
It causes the release status page to flicker in and out of being releasable and non-releasable. That's a release blocker IMO. |
…ultiple times (GH-98704) Co-authored-by: Kumar Aditya <[email protected]>
…lost multiple times (pythonGH-98704) Co-authored-by: Kumar Aditya <[email protected]> (cherry picked from commit 8a75542) Co-authored-by: Ken Jin <[email protected]>
…lost multiple times (pythonGH-98704) Co-authored-by: Kumar Aditya <[email protected]> (cherry picked from commit 8a75542) Co-authored-by: Ken Jin <[email protected]>
…ultiple times (GH-98704) Co-authored-by: Kumar Aditya <[email protected]> (cherry picked from commit 8a75542) Co-authored-by: Ken Jin <[email protected]>
…ultiple times (GH-98704) Co-authored-by: Kumar Aditya <[email protected]> (cherry picked from commit 8a75542) Co-authored-by: Ken Jin <[email protected]>
Waiting for Kumar's tests to land before I close this issue. It's no longer a release blocker though. |
… proactor event loop (pythonGH-98730) (cherry picked from commit 96ae80f) Co-authored-by: Kumar Aditya <[email protected]>
… proactor event loop (pythonGH-98730) (cherry picked from commit 96ae80f) Co-authored-by: Kumar Aditya <[email protected]>
…tor event loop (GH-98730) (cherry picked from commit 96ae80f) Co-authored-by: Kumar Aditya <[email protected]>
…tor event loop (GH-98730) (cherry picked from commit 96ae80f) Co-authored-by: Kumar Aditya <[email protected]>
…lost multiple times (pythonGH-98704) Co-authored-by: Kumar Aditya <[email protected]>
… proactor event loop (pythonGH-98730)
Run
python_d.exe -m test test_asyncio -m test_drain_raises -F
on Windows. The test eventually fails after some repetitions.The problem is that
_call_connection_lost
can be called multiple times, even after the socket by the proactortransport is closed. So it's callingclose()
on something that is already set toNone
.I have a PR to fix it.
The text was updated successfully, but these errors were encountered: