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

Quarantine Microsoft.AspNetCore.Server.Kestrel.Sockets.FunctionalTests.ResponseTests.AppCanHandleClientAbortingConnectionMidResponse #60110

Open
javiercn opened this issue Jan 30, 2025 · 1 comment
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions test-failure

Comments

@javiercn
Copy link
Member

Failing Test(s)

Microsoft.AspNetCore.Server.Kestrel.Sockets.FunctionalTests.ResponseTests.AppCanHandleClientAbortingConnectionMidResponse

Error Message

System.TimeoutException : The operation has timed out.

Stacktrace

   at Microsoft.AspNetCore.InternalTesting.TaskExtensions.TimeoutAfter(Task task, TimeSpan timeout, String filePath, Int32 lineNumber) in /_/src/Shared/TaskExtensions.cs:line 123
   at Microsoft.AspNetCore.Server.Kestrel.Sockets.FunctionalTests.ResponseTests.AppCanHandleClientAbortingConnectionMidResponse(ListenOptions listenOptions) in /_/src/Servers/Kestrel/test/FunctionalTests/ResponseTests.cs:line 408
   at Microsoft.AspNetCore.Server.Kestrel.Sockets.FunctionalTests.ResponseTests.AppCanHandleClientAbortingConnectionMidResponse(ListenOptions listenOptions) in /_/src/Servers/Kestrel/test/FunctionalTests/ResponseTests.cs:line 408
--- End of stack trace from previous location

Logs

[0.001s] [TestLifetime] [Information] Starting test AppCanHandleClientAbortingConnectionMidResponse-http_127.0.0.1_0 at 2025-01-30T13:52:07
[0.002s] [Microsoft.Extensions.Hosting.Internal.Host] [Debug] Hosting starting
[0.003s] [Microsoft.Hosting.Lifetime] [Information] Now listening on: http://127.0.0.1:50110
[0.003s] [Microsoft.AspNetCore.Hosting.Diagnostics] [Debug] Loaded hosting startup assembly Sockets.FunctionalTests
[0.003s] [Microsoft.Hosting.Lifetime] [Information] Application started. Press Ctrl+C to shut down.
[0.003s] [Microsoft.Hosting.Lifetime] [Information] Hosting environment: Production
[0.003s] [Microsoft.Hosting.Lifetime] [Information] Content root path: C:\h\w\A515092D\w\ACDD095D\e\
[0.003s] [Microsoft.Extensions.Hosting.Internal.Host] [Debug] Hosting started
[0.003s] [Microsoft.AspNetCore.Server.Kestrel] [Debug] TestServer is listening on port 50110
[0.005s] [Microsoft.AspNetCore.Server.Kestrel.Connections] [Debug] Connection id "0HNA16KLEBK9I" accepted.
[0.005s] [Microsoft.AspNetCore.Server.Kestrel.Connections] [Debug] Connection id "0HNA16KLEBK9I" started.
[0.005s] [Microsoft.AspNetCore.Hosting.Diagnostics] [Information] Request starting HTTP/1.1 GET http:/// - null null
[0.007s] [Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets] [Debug] Connection id "0HNA16KLEBK9I" reset.
[0.007s] [Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets] [Debug] Connection id "0HNA16KLEBK9I" sending FIN because: "The Socket transport's send loop completed gracefully."
[0.008s] [Microsoft.AspNetCore.Server.Kestrel.Connections] [Debug] Connection id "0HNA16KLEBK9I" disconnecting.
[46.686s] [Microsoft.Extensions.Hosting.Internal.Host] [Debug] Hosting stopping
[46.686s] [Microsoft.Hosting.Lifetime] [Information] Application is shutting down...
[47.777s] [Microsoft.AspNetCore.Hosting.Diagnostics] [Information] Request finished HTTP/1.1 GET http:/// - 200 null null 47768.9766ms
[47.777s] [Microsoft.AspNetCore.Server.Kestrel.Connections] [Debug] Connection id "0HNA16KLEBK9I" stopped.
[47.777s] [Microsoft.Extensions.Hosting.Internal.Host] [Debug] Hosting stopped
[47.803s] [Microsoft.AspNetCore.Server.Kestrel.Sockets.FunctionalTests.ResponseTests] [Error] Test threw an exception.
System.TimeoutException: The operation has timed out.
   at Microsoft.AspNetCore.InternalTesting.TaskExtensions.TimeoutAfter(Task task, TimeSpan timeout, String filePath, Int32 lineNumber) in /_/src/Shared/TaskExtensions.cs:line 123
   at Microsoft.AspNetCore.Server.Kestrel.Sockets.FunctionalTests.ResponseTests.AppCanHandleClientAbortingConnectionMidResponse(ListenOptions listenOptions) in /_/src/Servers/Kestrel/test/FunctionalTests/ResponseTests.cs:line 408
   at Microsoft.AspNetCore.Server.Kestrel.Sockets.FunctionalTests.ResponseTests.AppCanHandleClientAbortingConnectionMidResponse(ListenOptions listenOptions) in /_/src/Servers/Kestrel/test/FunctionalTests/ResponseTests.cs:line 408
   at Xunit.Sdk.TestInvoker`1.<>c__DisplayClass47_0.<<InvokeTestMethodAsync>b__1>d.MoveNext() in /_/src/xunit.execution/Sdk/Frameworks/Runners/TestInvoker.cs:line 259
--- End of stack trace from previous location ---
   at Xunit.Sdk.ExecutionTimer.AggregateAsync(Func`1 asyncAction) in /_/src/xunit.execution/Sdk/Frameworks/ExecutionTimer.cs:line 48
   at Xunit.Sdk.ExceptionAggregator.RunAsync(Func`1 code) in /_/src/xunit.core/Sdk/ExceptionAggregator.cs:line 90
[47.803s] [TestLifetime] [Information] Finished test AppCanHandleClientAbortingConnectionMidResponse-http_127.0.0.1_0 in 47.802249s

Build

https://dev.azure.com/dnceng-public/public/_build/results?buildId=934752&view=ms.vss-test-web.build-test-results-tab&runId=24755454&resultId=112391&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions label Jan 30, 2025
@shethaadit
Copy link
Contributor

Hi @javiercn, I will raise PR for this soon. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions test-failure
Projects
None yet
Development

No branches or pull requests

3 participants