Skip to content
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

Closed
kennytm opened this issue Jul 21, 2018 · 2 comments
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. O-windows Operating system: Windows T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@kennytm
Copy link
Member

kennytm commented Jul 21, 2018

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.

---- net::tcp::tests::connect_timeout_unbound stdout ----
thread 'net::tcp::tests::connect_timeout_unbound' panicked at 'called `Result::unwrap_err()` on an `Ok` value: TcpStream { addr: V4(127.0.0.1:3434), peer: V4(127.0.0.1:3434), socket: 1028 }', libcore\result.rs:945:5

Previous instances:

@kennytm kennytm added O-windows Operating system: Windows A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. C-bug Category: This is a bug. labels Jul 21, 2018
@kennytm
Copy link
Member Author

kennytm commented Jul 21, 2018

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.

@nnethercote
Copy link
Contributor

I've seen this on my Linux box recently, so much so that I think it has become a permafail.

alexcrichton added a commit to alexcrichton/rust that referenced this issue Mar 8, 2019
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
Centril added a commit to Centril/rust that referenced this issue Mar 9, 2019
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
Centril added a commit to Centril/rust that referenced this issue Mar 9, 2019
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
Centril added a commit to Centril/rust that referenced this issue Mar 9, 2019
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) C-bug Category: This is a bug. O-windows Operating system: Windows T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

2 participants