-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Closed
Closed
Copy link
Labels
A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)Area: Spurious failures in builds (spuriously == for no apparent reason)C-bugCategory: This is a bug.Category: This is a bug.O-windowsOperating system: WindowsOperating system: WindowsT-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.Relevant to the infrastructure team, which will review and decide on the PR/issue.
Description
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:
- 2018-05-19T07:41:59Z — Turn deprecation lint
legacy_imports
into a hard error #50760 (comment) (i686-msvc-1) - 2018-06-04T15:32:27Z — Select Polonius algorithm via
POLONIUS_ALGORITHM
environment variable #51246 (comment) (i686-mingw-1) - 2018-06-30T14:00:20Z — optimize
places_conflict
to avoid complex vectors etc #51849 (comment) (x86_64-mingw) - 2018-07-21T18:51:09Z — Remove highlighting from secondary messages #51485 (comment) (i686-msvc-1)
Metadata
Metadata
Assignees
Labels
A-spuriousArea: Spurious failures in builds (spuriously == for no apparent reason)Area: Spurious failures in builds (spuriously == for no apparent reason)C-bugCategory: This is a bug.Category: This is a bug.O-windowsOperating system: WindowsOperating system: WindowsT-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.Relevant to the infrastructure team, which will review and decide on the PR/issue.