Skip to content

Conversation

ChrisDenton
Copy link
Member

I wonder if we could/should try enabling this again? It was closed by #38867 due to #31657. I've tried running this test (along with other tests) on my machine a number of times and haven't seen this fail yet,

Caveat: the worst that can happen is this succeeds initially but then causes random hangs in CI. This is not a great failure mode and would be a reason not to do this.

If this does work out, closes #39006

r? @Mark-Simulacrum

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Mar 7, 2022
@Mark-Simulacrum
Copy link
Member

@bors r+ rollup=iffy

Let's try it and keep an eye on spurious failures in CI (cc @rust-lang/infra), if we see an uptick should be easy enough to revert. It's been quite some time since the initial disabling so it seems plausible that the problems have gone away now.

@bors
Copy link
Collaborator

bors commented Mar 8, 2022

📌 Commit 24ec0f2 has been approved by Mark-Simulacrum

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 8, 2022
bors added a commit to rust-lang-ci/rust that referenced this pull request Mar 8, 2022
Rollup of 5 pull requests

Successful merges:

 - rust-lang#94689 (Use impl substs in `#[rustc_on_unimplemented]`)
 - rust-lang#94714 (Enable `close_read_wakes_up` test on Windows)
 - rust-lang#94723 (Add core::hint::must_use)
 - rust-lang#94724 (unix: Avoid name conversions in `remove_dir_all_recursive`)
 - rust-lang#94730 (Reverted atomic_mut_ptr feature removal causing compilation break)

Failed merges:

r? `@ghost`
`@rustbot` modify labels: rollup
@bors
Copy link
Collaborator

bors commented Mar 9, 2022

⌛ Testing commit 24ec0f2 with merge 803a759...

@bors bors merged commit ee8109d into rust-lang:master Mar 9, 2022
@rustbot rustbot added this to the 1.61.0 milestone Mar 9, 2022
@ChrisDenton ChrisDenton deleted the win-close_read_wakes_up branch March 9, 2022 00:27
Dylan-DPC added a commit to Dylan-DPC/rust that referenced this pull request Mar 9, 2022
…_up_test_sgx_platform, r=dtolnay

Ignore `close_read_wakes_up` test on SGX platform

PR rust-lang#94714 enabled the `close_read_wakes_up` test for all platforms. This is incorrect. This test should be ignored at least for the SGX platform.

cc: `@mzohreva` `@jethrogb`
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this pull request Mar 9, 2022
…_up_test_sgx_platform, r=dtolnay

Ignore `close_read_wakes_up` test on SGX platform

PR rust-lang#94714 enabled the `close_read_wakes_up` test for all platforms. This is incorrect. This test should be ignored at least for the SGX platform.

cc: ``@mzohreva`` ``@jethrogb``
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

A closed TCP socket doesn't always wake up a blocked read on Windows
5 participants