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.SendFileTest / SendFile_APM #24484

Closed
karelz opened this issue Dec 18, 2017 · 1 comment
Closed

Test failure: System.Net.Sockets.Tests.SendFileTest / SendFile_APM #24484

karelz opened this issue Dec 18, 2017 · 1 comment
Assignees
Labels
area-System.Net.Sockets 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 18, 2017

Type of failures

WhenAllOrAnyFailed timed out after 30000

Failure 20171213.05:

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.SendFileTest.<SendFile_APM>d__7.MoveNext() in E:\A\_work\1400\s\corefx\src\System.Net.Sockets\tests\FunctionalTests\SendFile.cs:line 234
--- 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 ---

Neither client nor server task completed within allowed time

Before SendFile_APM test change in dotnet/corefx@779171f#diff-479492e701f07787f80f44f18ef076f8 on 2017/11/21

Failures 20171022.02:

Neither client nor server task completed within allowed time
Expected: True
Actual:   False
   at System.Net.Sockets.Tests.SendFileTest.SendFile_APM(IPAddress listenAt, Boolean sendPreAndPostBuffers, Int32 bytesToSend) in /root/corefx-1079212/src/System.Net.Sockets/tests/FunctionalTests/SendFile.cs:line 233

History of failures

Day Build OS Error message
7/11 20170711.04 OSX10.13 Neither client nor server task completed within allowed time
9/4 20170904.01 OSX10.12 Neither client nor server task completed within allowed time
10/22 20171022.02 RedHat69 Neither client nor server task completed within allowed time - link
11/21 N/A N/A Assert changed into TimeoutException in dotnet/corefx@779171f#diff-479492e701f07787f80f44f18ef076f8
12/1 20171201.03 Win7 WhenAllOrAnyFailed timed out after 30000
12/8 20171208.01 Win8.1 WhenAllOrAnyFailed timed out after 30000
12/10 20171210.03 Win8.1 WhenAllOrAnyFailed timed out after 30000
12/12 20171212.03 Win10 WhenAllOrAnyFailed timed out after 30000
12/13 20171213.05 Win7 WhenAllOrAnyFailed timed out after 30000 - link
12/28 20171228.01 Win8.1 WhenAllOrAnyFailed timed out after 30000 - link
12/30 20171230.02 Win7 WhenAllOrAnyFailed timed out after 30000 - link
1/4 20180104.02 Win10 WhenAllOrAnyFailed timed out after 30000 - link
1/23 20180123.04 Win7 WhenAllOrAnyFailed timed out after 30000 - link
3/13 20180313.03 Win8.1 WhenAllOrAnyFailed timed out after 30000
3/16 20180316.01 Win7 WhenAllOrAnyFailed timed out after 30000
3/22 20180322.01 Win8.1 WhenAllOrAnyFailed timed out after 30000
3/22 20180322.06 Win10 WhenAllOrAnyFailed timed out after 30000

Timeout similar to #24444, started around same time. Sometimes correlated failures (12/28, 12/13).

@wfurt
Copy link
Member

wfurt commented Sep 11, 2019

I found 4 failures in last 90 days. That can be considered as noice caused by CI environment.
Since this issue is super old, I'm going to close it.
If we see this test failing again, we should collect console.log and testResults.xml and we should start fresh issue.

@wfurt wfurt closed this as completed Sep 11, 2019
@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 5.0 milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Sockets test-bug Problem in test source code (most likely) test-run-core Test failures in .NET Core test runs
Projects
None yet
Development

No branches or pull requests

3 participants