bpo-30064: Properly skip unstable loop.sock_connect() racing test #20494
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.
After the first connect attempt before the listener is ready, the socket needs time to "recover" to make the next connect call. On Linux, a second retry will do. On Windows, the waiting time is unpredictable; and on FreeBSD the socket may never come back because it's a loopback address. Here we'll just retry for a few times, and have to skip the test if it's not working. See also:
https://bugs.python.org/issue30064