Skip to content
This repository was archived by the owner on Dec 18, 2018. It is now read-only.

Flaky test: AppCanHandleClientAbortingConnectionMidResponse #2581

Closed
ryanbrandenburg opened this issue May 16, 2018 · 3 comments
Closed

Flaky test: AppCanHandleClientAbortingConnectionMidResponse #2581

ryanbrandenburg opened this issue May 16, 2018 · 3 comments
Assignees
Milestone

Comments

@ryanbrandenburg
Copy link
Contributor

This test fails occasionally with the following error:

Moq.MockException : 
Expected invocation on the mock once, but was 0 times: t => t.ConnectionStop(It.IsAny<String>())
No setups configured.
Performed invocations:
KestrelTrace.IsEnabled(Critical)
KestrelTrace.BeginScope<ConnectionLogScope>([[ConnectionId, 0HLDRBFHJGCHT]])
KestrelTrace.ConnectionStart("0HLDRBFHJGCHT")
KestrelTrace.ConnectionDisconnect("0HLDRBFHJGCHT")
   at Moq.Mock.ThrowVerifyException(MethodCall expected, IEnumerable`1 setups, IEnumerable`1 actualCalls, Expression expression, Times times, Int32 callCount)
   at Moq.Mock.VerifyCalls(Interceptor targetInterceptor, MethodCall expected, Expression expression, Times times)
   at Moq.Mock.Verify[T](Mock`1 mock, Expression`1 expression, Times times, String failMessage)
   at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.ResponseTests.AppCanHandleClientAbortingConnectionMidResponse(ListenOptions listenOptions) in /_/test/Kestrel.FunctionalTests/ResponseTests.cs:line 2504
--- End of stack trace from previous location where exception was thrown ---
@mikeharder mikeharder self-assigned this May 19, 2018
@mikeharder mikeharder added this to the 2.2.0-mq milestone May 19, 2018
@mikeharder
Copy link
Contributor

@mikeharder
Copy link
Contributor

@halter73
Copy link
Member

halter73 commented Jun 1, 2018

This was fixed by #2574.

@halter73 halter73 closed this as completed Jun 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants