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.

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

Test failure: System.Net.Sockets.Tests.SendReceiveMemoryNativeTask / SendRecvPollSync_TcpListener_Socket #24444

Closed
karelz opened this issue Dec 13, 2017 · 5 comments · Fixed by #51186
Labels
area-System.Net.Sockets os-windows test-bug Problem in test source code (most likely) test-run-core Test failures in .NET Core test runs
Milestone

Comments

@karelz
Copy link
Member

karelz commented Dec 13, 2017

Type of failures

Timeout 30000

Failure 20171211.01:

System.TimeoutException : WhenAllOrAnyFailed timed out after 30000
   at System.Threading.Tasks.TaskTimeoutExtensions.<WhenAllOrAnyFailed>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Net.Sockets.Tests.SendReceive`1.<SendRecvPollSync_TcpListener_Socket>d__7.MoveNext() in E:\A\_work\1973\s\corefx\src\System.Net.Sockets\tests\FunctionalTests\SendReceive.cs:line 629
--- End of stack trace from previous location where exception was thrown ---
--- End of stack trace from previous location where exception was thrown ---
--- End of stack trace from previous location where exception was thrown ---

Read poll after completion should have succeeded

Failure 20171202.01:

Read poll after completion should have succeeded
Expected: True
Actual:   False
   at System.Net.Sockets.Tests.SendReceive`1.<>c__DisplayClass7_1.<<SendRecvPollSync_TcpListener_Socket>b__0>d.MoveNext() in E:\A\_work\704\s\corefx\src\System.Net.Sockets\tests\FunctionalTests\SendReceive.cs:line 582
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.Tasks.TaskTimeoutExtensions.<WhenAllOrAnyFailed>d__2.MoveNext() in E:\A\_work\704\s\corefx\src\Common\tests\System\Threading\Tasks\TaskTimeoutExtensions.cs:line 49
--- End of stack trace from previous location where exception was thrown ---
   at System.Net.Sockets.Tests.SendReceive`1.<SendRecvPollSync_TcpListener_Socket>d__7.MoveNext() in E:\A\_work\704\s\corefx\src\System.Net.Sockets\tests\FunctionalTests\SendReceive.cs:line 627
--- End of stack trace from previous location where exception was thrown ---
--- End of stack trace from previous location where exception was thrown ---
--- End of stack trace from previous location where exception was thrown ---

With earlier variant wrapped in AggregateException in failure 20171113.03:

System.AggregateException : One or more errors occurred. (Read poll after completion should have succeeded
Expected: True
Actual:   False)
---- Read poll after completion should have succeeded
Expected: True
Actual:   False
   at System.Threading.Tasks.Task.WaitAllCore(Task[] tasks, Int32 millisecondsTimeout, CancellationToken cancellationToken) in E:\A\_work\1531\s\src\mscorlib\src\System\Threading\Tasks\Task.cs:line 4651
   at System.Net.Sockets.Tests.SendReceive`1.SendRecvPollSync_TcpListener_Socket(IPAddress listenAt, Boolean pollBeforeOperation) in E:\A\_work\1163\s\corefx\src\System.Net.Sockets\tests\FunctionalTests\SendReceive.cs:line 625
----- Inner Stack Trace -----
   at System.Net.Sockets.Tests.SendReceive`1.<>c__DisplayClass7_1.<<SendRecvPollSync_TcpListener_Socket>b__0>d.MoveNext() in E:\A\_work\1163\s\corefx\src\System.Net.Sockets\tests\FunctionalTests\SendReceive.cs:line 582

SocketException: An existing connection was forcibly closed by the remote host

Older variant of the test failure in May-July (potentially different bug).
Failure 20170706.02:

System.AggregateException : One or more errors occurred. (An existing connection was forcibly closed by the remote host)
---- System.Net.Sockets.SocketException : An existing connection was forcibly closed by the remote host
   at System.ThrowHelper.ThrowAggregateException(List`1 exceptions)
   at System.Threading.Tasks.Task.WaitAll(Task[] tasks, Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Net.Sockets.Tests.SendReceive.SendRecvPollSync_TcpListener_Socket(IPAddress listenAt, Boolean pollBeforeOperation)
----- Inner Stack Trace -----
   at System.Net.Sockets.Tests.SendReceive.<>c__DisplayClass25_1.<<SendRecvPollSync_TcpListener_Socket>b__0>d.MoveNext()

History of failures

Day Build OS Error message
5/1 20170501.01 Win7 SocketException: An existing connection was forcibly closed by the remote host
5/2 20170502.02 Win7 Aggregate: Read poll after completion should have succeeded
5/13 20170513.01 Win8.1 SocketException: An existing connection was forcibly closed by the remote host
5/30 20170530.06 Win7 SocketException: An existing connection was forcibly closed by the remote host
6/13 20170613.02 Mac Wait timed out - changed to TimeoutException in dotnet/corefx@779171f#diff-5d77ee23eb2ea596e218f9c1ef09d793 on 7/21
6/21 20170621.02 Win8.1 SocketException: An existing connection was forcibly closed by the remote host
7/6 20170706.02 Win10 SocketException: An existing connection was forcibly closed by the remote host
7/14 20170714.01 Win7 Aggregate: Read poll after completion should have succeeded
8/1 20170801.03 Win10 Aggregate: Read poll after completion should have succeeded
8/6 20170806.01 Win10 Aggregate: Read poll after completion should have succeeded
8/10 20170810.02 Win10 Aggregate: Read poll after completion should have succeeded
9/14 20170914.01 Win7 Aggregate: Read poll after completion should have succeeded
9/26 20170926.05 Win8.1 Aggregate: Read poll after completion should have succeeded
11/7 20171107.01 Win8.1 Aggregate: Read poll after completion should have succeeded
11/10 20171110.05 Win7 Aggregate: Read poll after completion should have succeeded
11/13 20171113.03 Win10 Aggregate: Read poll after completion should have succeeded
11/25 20171125.02 Win7 Timeout 30000
11/30 20171130.02 Win10 Timeout 30000
12/1 20171201.03 Win7 Timeout 30000
12/1 20171201.03 Win7 Timeout 30000
12/1 20171201.03 Win7 Timeout 30000
12/2 20171202.01 Win8.1 Read poll after completion should have succeeded
12/9 20171209.03 Win10 Timeout 30000
12/11 20171211.01 Win7 Timeout 30000
12/13 20171213.05 Win7 Timeout 30000 - link
12/28 20171228.01 Win8.1 Timeout 30000 - link
1/4 20180104.02 Win10 Timeout 30000 - link
1/13 20180113.01 Win7 Timeout 30000 - link
3/13 20180313.03 Win8.1 Timeout 30000
3/14 20180314.02 Win7 Timeout 30000
3/15 20180315.01 Win7 Timeout 30000
3/17 20180317.01 Win10 Read poll after completion should have succeeded
3/22 20180322.01 Win8.1 3x Timeout 30000
3/22 20180322.06 Win7 Timeout 30000
3/29 20180329.01 Win10 2x Timeout 30000
3/31 20180331.03 Win7 2x Timeout 30000

Timeout similar to dotnet/corefx#25979. Sometimes correlated failures (12/28, 12/13, 1/4).

@karelz
Copy link
Member Author

karelz commented Dec 13, 2017

@rmkerr historical info

@rmkerr
Copy link
Contributor

rmkerr commented Dec 13, 2017

Thanks for adding that!

@karelz karelz changed the title Test failure: System.Net.Sockets.Tests.SendReceiveMemoryNativeTask/SendRecvPollSync_TcpListener_Socket Test failure: System.Net.Sockets.Tests.SendReceiveMemoryNativeTask / SendRecvPollSync_TcpListener_Socket Dec 13, 2017
@wfurt
Copy link
Member

wfurt commented Dec 20, 2018

SendRecvPollSync_TcpListener_Socket failed 14 times in last 3 month. (Nano, Debian9 and OSX 10.12)

@wfurt
Copy link
Member

wfurt commented Jan 22, 2019

same base function failure as #1479

@wfurt
Copy link
Member

wfurt commented Sep 9, 2019

I see 15 failures in last 90 days - on different flavors of windows. Most recent failure on 9/3.

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 5.0 milestone Jan 31, 2020
@karelz karelz modified the milestones: 5.0, Future Jun 5, 2020
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Apr 13, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Apr 14, 2021
@ghost ghost locked as resolved and limited conversation to collaborators May 14, 2021
@karelz karelz modified the milestones: Future, 6.0.0 May 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Sockets os-windows test-bug Problem in test source code (most likely) test-run-core Test failures in .NET Core test runs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants