-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
gh-101384: add socket timeout to ThreadedVSOCKSocketStreamTest and skip it on WSL #101419
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
Conversation
@giampaolo, @gpshead (as networking experts) |
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.
A NEWS entry is not required here. |
Thanks @peterjpxie for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
…and skip it on WSL (pythonGH-101419) (cherry picked from commit 9fd420f) Co-authored-by: Peter Jiping Xie <peter.jp.xie@gmail.com>
GH-115585 is a backport of this pull request to the 3.12 branch. |
…and skip it on WSL (pythonGH-101419) (cherry picked from commit 9fd420f) Co-authored-by: Peter Jiping Xie <peter.jp.xie@gmail.com>
GH-115586 is a backport of this pull request to the 3.11 branch. |
…and skip it on WSL (pythonGH-101419)
…and skip it on WSL (pythonGH-101419)
…and skip it on WSL (pythonGH-101419)
1/ Add socket server timeout to ThreadedVSOCKSocketStreamTest so that it does not hang on client connection failure, e.g. on WSL.
After adding the timeout, it was able to fail on this test and continue as follows.
2/ Furthermore, as it does not work on WSL (OSError: [Errno 101] Network is unreachable), skip it on WSL.
This works on VMware workstation for communication between VM guests and host.
3/ With all the changes, this is the summary of tests on different platforms: