-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Add regression tests to capture legitimate OSErrors in unusual states #344
Labels
bug
Something is broken
Comments
15 tasks
webknjaz
added a commit
that referenced
this issue
Dec 7, 2020
webknjaz
added a commit
that referenced
this issue
Dec 7, 2020
webknjaz
added a commit
that referenced
this issue
Dec 7, 2020
webknjaz
added a commit
that referenced
this issue
Dec 7, 2020
webknjaz
added a commit
that referenced
this issue
Dec 7, 2020
webknjaz
added a commit
that referenced
this issue
Dec 7, 2020
webknjaz
added a commit
that referenced
this issue
Dec 11, 2020
webknjaz
added a commit
that referenced
this issue
Dec 11, 2020
webknjaz
added a commit
that referenced
this issue
Dec 11, 2020
webknjaz
added a commit
that referenced
this issue
Dec 11, 2020
This change adds artificial tests for TCP connection becoming broken simultaneously with the server-side initiating the client connection shutdown sequence with TCP FIN packet. Ref #344
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #341, users reported a regression in how certain exceptions were handled or not. In #342, these issues were addressed, but a regression test had not yet been implemented.
This bug captures that deficiency until such a time that a test can be devised.
The text was updated successfully, but these errors were encountered: