Skip to content

[test-quarantine] Unquarantine QuicStreamContextTests.BidirectionalStream_ServerReadsDataAndCompletes_GracefullyClosed (issue #52462) #66493

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.

Sign up for GitHub

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

Merged
wtgodbe merged 1 commit into from
Apr 27, 2026
+0 −1

Unquarantine QuicStreamContextTests.BidirectionalStream_ServerReadsDa…

47a698f
Select commit
Loading
Failed to load commit list.
Merged

[test-quarantine] Unquarantine QuicStreamContextTests.BidirectionalStream_ServerReadsDataAndCompletes_GracefullyClosed (issue #52462) #66493

Unquarantine QuicStreamContextTests.BidirectionalStream_ServerReadsDa…
47a698f
Select commit
Loading
Failed to load commit list.
Azure Pipelines / aspnetcore-ci succeeded Apr 27, 2026 in 1h 0m 31s

Build #20260427.19 had test failures

0 errors / 1,274 warnings

Details

Tests

  • Failed: 4 (0.00%)
  • Passed: 124,403 (98.59%)
  • Other: 1,774 (1.41%)
  • Total: 126,181

Annotations

Check failure on line 1 in Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.AcceptNewStreamsDuringClosingConnection

See this annotation in the file changed.

@azure-pipelines azure-pipelines / aspnetcore-ci

Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.AcceptNewStreamsDuringClosingConnection 

Assert.Equal() Failure: Values differ
Expected: 2147483647
Actual:   0
Raw output 
   at Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2TestBase.VerifyGoAway(Http2Frame frame, Int32 expectedLastStreamId, Http2ErrorCode expectedErrorCode) in /_/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2TestBase.cs:line 1296
   at Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.AcceptNewStreamsDuringClosingConnection() in /_/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2ConnectionTests.cs:line 5395
--- End of stack trace from previous location ---

Check failure on line 1 in InMemory.FunctionalTests--net11.0.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / aspnetcore-ci

InMemory.FunctionalTests--net11.0.WorkItemExecution 

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.

Check failure on line 1 in Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2TimeoutTests.HEADERS_TrailerWithEmptyCONTINUATIONs_WithinRequestHeadersTimeout_AbortsConnection

See this annotation in the file changed.

@azure-pipelines azure-pipelines / aspnetcore-ci

Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2TimeoutTests.HEADERS_TrailerWithEmptyCONTINUATIONs_WithinRequestHeadersTimeout_AbortsConnection 

Moq.MockException : 
Expected invocation on the mock once, but was 0 times: h => h.OnTimeout(TimeoutReason.RequestHeaders)

Configured setups: 
ITimeoutHandler h => h.OnTimeout(It.IsAny<TimeoutReason>())
No invocations performed.
Raw output 
   at Moq.Mock.VerifyCalls(Mock targetMock, InvocationShape expectation, LambdaExpression expression, Times times, String failMessage)
   at Moq.Mock.Verify[T](Mock`1 mock, Expression`1 expression, Times times, String failMessage)
   at Moq.Mock`1.Verify(Expression`1 expression, Times times)
   at Moq.Mock`1.Verify(Expression`1 expression, Func`1 times)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2TimeoutTests.HEADERS_TrailerWithEmptyCONTINUATIONs_WithinRequestHeadersTimeout_AbortsConnection() in /_/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2TimeoutTests.cs:line 1119
--- End of stack trace from previous location ---

Check failure on line 1 in InMemory.FunctionalTests--net11.0.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / aspnetcore-ci

InMemory.FunctionalTests--net11.0.WorkItemExecution 

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
View more details on Azure Pipelines