-
Notifications
You must be signed in to change notification settings - Fork 12.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
Spurious unwrap_err() of Ok at 'net::tcp::tests::connect_timeout_unbound' on Windows #52590
Comments
From the logs, the TCP port of both the TcpStream (self) and TcpListener (socket, dropped) are the same.
According to https://support.microsoft.com/en-us/help/929851/the-default-dynamic-port-range-for-tcp-ip-has-changed-in-windows-vista the dynamic port range is 1025 to 5000 inclusive, so the collision rate is ≈1/3976 per build if uniformly distributed. |
I've seen this on my Linux box recently, so much so that I think it has become a permafail. |
This commit deletes the `connect_timeout_unbound` test from the standard library which, unfortunately, is by definition eventually going to be a spuriously failing test. There's no way to reserve a port as unbound so we can rely on ecosystem testing for this feature for now. Closes rust-lang#52590
std: Delete a by-definition spuriously failing test This commit deletes the `connect_timeout_unbound` test from the standard library which, unfortunately, is by definition eventually going to be a spuriously failing test. There's no way to reserve a port as unbound so we can rely on ecosystem testing for this feature for now. Closes rust-lang#52590
std: Delete a by-definition spuriously failing test This commit deletes the `connect_timeout_unbound` test from the standard library which, unfortunately, is by definition eventually going to be a spuriously failing test. There's no way to reserve a port as unbound so we can rely on ecosystem testing for this feature for now. Closes rust-lang#52590
std: Delete a by-definition spuriously failing test This commit deletes the `connect_timeout_unbound` test from the standard library which, unfortunately, is by definition eventually going to be a spuriously failing test. There's no way to reserve a port as unbound so we can rely on ecosystem testing for this feature for now. Closes rust-lang#52590
Symptom: On Windows, the libstd test
net::tcp::tests::connect_timeout_unbound
panicked for unexpectedly connected to a local closed TCP socket without timing out.Previous instances:
legacy_imports
into a hard error #50760 (comment) (i686-msvc-1)POLONIUS_ALGORITHM
environment variable #51246 (comment) (i686-mingw-1)places_conflict
to avoid complex vectors etc #51849 (comment) (x86_64-mingw)The text was updated successfully, but these errors were encountered: