System.Net.Sockets.Tests.DualMode.AcceptV6BoundToSpecificV4_CantConnect hangs on Unix #16265

Activity

1. ericeil

   self-assigned this

   on Feb 2, 2016
2. ericeil

   added 3 commits that reference this issue on Feb 2, 2016

   Disable AcceptV6BoundToSpecificV4_CantConnect on Unix due to #5832.

   81ac511

   Disable AcceptV4BoundToSpecificV6_CantConnect on Unix due to #5832.

   cb87043

   Disable AcceptV6BoundToAnyV4_CantConnect on Unix due to #5832.

   1ff2699
3. ericeil commented on Feb 4, 2016

   

   ericeil

   on Feb 4, 2016

   ContributorAuthor

   More actions

   Note that calling shutdown on the socket prior to closing it seems to unblock the pending accept on Linux. But it causes an error on OSX and Windows. I haven't found a way to unblock a pending accept on OSX, other than to simply successfully connect to the socket.
4. stephentoub commented on Feb 4, 2016

   

   stephentoub

   on Feb 4, 2016

   Member

   More actions

   Does a signal cause it to wake up with EINTR?
5. ericeil commented on Feb 10, 2016

   

   ericeil

   on Feb 10, 2016

   ContributorAuthor

   More actions

   Fixing this with signals may be an option. Moving this to "future" for now; I'm not sure this is something we actually need to fix (depends on how much existing code depends on Dispose for cancellation).
6. ericeil commented on Jul 25, 2016

   

   ericeil

   on Jul 25, 2016

   ContributorAuthor

   More actions

   See https://github.com/dotnet/corefx/issues/5749#issuecomment-215597396. Turns out closing a managed Socket while there are pending synchronous operations isn't really supported on Windows either. Let's not complicate the x-plat implementation to support this.
7. ericeil

   closed this as completedon Jul 25, 2016
8. ericeil

   added 2 commits that reference this issue on Jul 25, 2016

   Change ActiveIssue to PlatformSpecific for closed issue #5832.

   06f2eb3

   Change ActiveIssue to PlatformSpecific for closed issue #5832. (#10308)

   516328f
9. msftgits

   transferred this issue fromdotnet/corefxon Jan 31, 2020
10. msftgits

    added this to the 1.1.0 milestone on Jan 31, 2020
11. ghost locked as resolved and limited conversation to collaborators on Jan 3, 2021