-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
System.Net.WebSockets.Client.Tests.ConnectTest.ConnectAsync_CancellationRequestedAfterConnect_ThrowsOperationCanceledException failures in OSX #38159
Comments
Tagging subscribers to this area: @dotnet/ncl |
interesting
envoyproxy/envoy#1446 suggests that we can get that if peer shutdown their side. We have seen something similar with getpeername() in Socket from fd code. Maybe loopback should just eat that exception. Perhaps NoDelay should be best effort. |
Same test just failed for me:
|
This is interesting. The socket should be in connected state once Accept is finished. Unless explicit Disconnect or Dispose() is called. |
Hit in #41234 |
System.Net.WebSockets.Client.Tests.ConnectTest.ConnectAsync_CancellationRequestedAfterConnect_ThrowsOperationCanceledException
Console Log Summary
Builds
Configurations
Helix Logs
This is over the past 100 builds.
cc: @dotnet/ncl @stephentoub
The text was updated successfully, but these errors were encountered: