Test timeout: Receive*FromAsyncV*BoundToSpecificV*_Success

[karelz]

Tests affected:

• System.Net.Sockets.Tests.DualModeConnectionlessReceiveMessageFrom.ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
• System.Net.Sockets.Tests.DualModeConnectionlessReceiveFromAsync.ReceiveFromAsyncV6BoundToSpecificV6_Success
• System.Net.Sockets.Tests.DualModeConnectionlessReceiveFromAsync.ReceiveFromAsyncV4BoundToAnyV4_Success

Failures 3/12-8/26 (incl. PRs)

Day	Run	OS	Test
4/4	Official run	Windows.7.Amd64.Open - x86	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
6/22	Official run	Debian.9.Arm32.Open - arm	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
6/23	Official run	Ubuntu.1804.ArmArch.Open - arm64	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success ... run with massive timeouts
6/25			... results below include release/6.0* branches ...
6/28	Official run - Preview6	Fedora.32.Amd64.Open	2x ReceiveFromAsyncV6BoundToSpecificV6_Success
6/30	Official run - Preview6	Ubuntu.1804.ArmArch.Open - arm64	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
7/4	Official run	Windows.Nano.1809.Amd64.Open	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
7/7	Official run	Ubuntu.1804.ArmArch.Open - arm64	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
7/12	Official run - Preview3	Windows.10.Amd64.Server19H1.Open - x86	ReceiveFromAsyncV6BoundToSpecificV6_Success ReceiveFromAsyncV4BoundToAnyV4_Success
7/13	Official run - Preview6	Fedora.30.Amd64.Open	ReceiveFromAsyncV6BoundToSpecificV6_Success
7/16	Official run - Preview6	Alpine.312.Arm64.Open	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
7/21	Official run - Preview6	Ubuntu.1804.ArmArch.Open	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
7/28	Official run - Preview7	Windows.10.Amd64.ServerRS5.Open - x86	ReceiveFromAsyncV6BoundToSpecificV6_Success
8/2	Official run - Preview7	Ubuntu.1910.Amd64.Open	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
8/8	Official run - Preview7	Windows.7.Amd64.Open - x86	ReceiveFromAsyncV6BoundToSpecificV6_Success ReceiveFromAsyncV4BoundToAnyV4_Success
8/17	PR #57505 (main - 7.0)	Windows.10.Amd64.Server19H1.ES.Open - x86	ReceiveFromAsyncV6BoundToSpecificV6_Success ReceiveFromAsyncV4BoundToAnyV4_Success
8/18	Official run - Preview7	SLES.15.Amd64.Open	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
8/20	Official run	Windows.10.Amd64.Server19H1.Open - x86	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
8/24	Official run	Windows.10.Amd64.ServerRS5.Open - x86	ReceiveFromAsyncV6BoundToSpecificV6_Success
8/25	Official run - release/6.0	Windows.10.Amd64.ServerRS5.Open - x86	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
8/27	Official run	Windows.10.Amd64.Server19H1.Open - x86	ReceiveFromAsyncV6BoundToSpecificV6_Success
8/28	Official run - release/6.0	Debian.10.Amd64.Open	ReceiveFromAsyncV6BoundToSpecificV6_Success
8/31	Official run	Windows.10.Amd64.Server19H1.Open	ReceiveFromAsyncV6BoundToSpecificV6_Success ReceiveFromAsyncV4BoundToAnyV4_Success
8/31	Official run	Debian.11.Amd64.Open	ReceiveMessageFromAsyncV4BoundToSpecificV4_Success
9/3	Official run - release/6.0-rc1	Windows.10.Amd64.ServerRS5.Open	ReceiveFromAsyncV6BoundToSpecificV6_Success

Failure ReceiveMessageFromAsyncV4BoundToSpecificV4_Success:

System.TimeoutException : The operation has timed out.

   at System.Net.Sockets.Tests.DualModeConnectionlessReceiveMessageFrom.ReceiveMessageFromAsync_Helper(IPAddress listenOn, IPAddress connectTo, Boolean expectedToTimeout) in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/DualModeSocketTest.cs:line 2381
   at System.Net.Sockets.Tests.DualModeConnectionlessReceiveMessageFrom.ReceiveMessageFromAsyncV4BoundToSpecificV4_Success() in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/DualModeSocketTest.cs:line 2282

Failure ReceiveFromAsyncV6BoundToSpecificV6_Success:

System.TimeoutException : The operation has timed out.

   at System.Net.Sockets.Tests.DualModeConnectionlessReceiveFromAsync.ReceiveFromAsync_Helper(IPAddress listenOn, IPAddress connectTo, Boolean expectedToTimeout) in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/DualModeSocketTest.cs:line 1756
   at System.Net.Sockets.Tests.DualModeConnectionlessReceiveFromAsync.ReceiveFromAsyncV6BoundToSpecificV6_Success() in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/DualModeSocketTest.cs:line 1691

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Test type: System.Net.Sockets.Tests.DualModeConnectionlessReceiveMessageFrom

Failures 6/24-8/23 (incl. PRs)

Day	Run	OS
6/30	Official run - Preview6	Ubuntu.1804.ArmArch.Open
7/4	Official run	Windows.Nano.1809.Amd64.Open
7/7	Official run	Ubuntu.1804.ArmArch.Open
7/16	Official run - Preview6	Alpine.312.Arm64.Open
7/21	Official run - Preview6	Ubuntu.1804.ArmArch.Open
8/2	Official run - Preview7	Ubuntu.1910.Amd64.Open
8/18	Official run - Preview7	SLES.15.Amd64.Open
8/20	Official run	Windows.10.Amd64.Server19H1.Open

Failure:

System.TimeoutException : The operation has timed out.

   at System.Net.Sockets.Tests.DualModeConnectionlessReceiveMessageFrom.ReceiveMessageFromAsync_Helper(IPAddress listenOn, IPAddress connectTo, Boolean expectedToTimeout) in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/DualModeSocketTest.cs:line 2381
   at System.Net.Sockets.Tests.DualModeConnectionlessReceiveMessageFrom.ReceiveMessageFromAsyncV4BoundToSpecificV4_Success() in /_/src/libraries/System.Net.Sockets/tests/FunctionalTests/DualModeSocketTest.cs:line 2282

Author:	karelz
Assignees:	-
Labels:	area-System.Net.Sockets
Milestone:	Future

[wfurt]

triage: we should look for recent failures and close it if it is not failing.

[antonfirsov]

No failures in the last 90 days, #80715 should improve all DualMode tests, closing.