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.

Sign up for GitHub

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

Jump to bottom

A closed TCP socket doesn't always wake up a blocked read on Windows #39006

Closed
brson opened this issue Jan 12, 2017 · 1 comment · Fixed by #94714
Closed

A closed TCP socket doesn't always wake up a blocked read on Windows #39006

brson opened this issue Jan 12, 2017 · 1 comment · Fixed by #94714
Labels
C-bug Category: This is a bug. O-windows Operating system: Windows T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@brson
Copy link
Contributor

brson commented Jan 12, 2017

The test was ignored in #38867.
@brson brson added O-windows Operating system: Windows T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Jan 12, 2017
@liranringel
Copy link
Contributor

close_read_wakes_up actually pass on my pc (windows 10 x64).

@Mark-Simulacrum Mark-Simulacrum added the C-bug Category: This is a bug. label Jul 26, 2017
@ChrisDenton ChrisDenton mentioned this issue Mar 7, 2022
Merged
@bors bors closed this as completed in ee8109d Mar 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-bug Category: This is a bug. O-windows Operating system: Windows T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Enable close_read_wakes_up test on Windows ChrisDenton/rust
3 participants
@brson @Mark-Simulacrum @liranringel