Quarantine Http2ConnectionTests (AbortedStream_ResetsAndDrainsRequest_RefusesFramesAfterEndOfStream, StopProcessingNextRequestSendsGracefulGOAWAYThenFinalGOAWAYWhenAllStreamsComplete, AbortSendsFinalGOAWAY, GOAWAY_Received_ConnectionLifetimeNotification_Cancelled)

[wtgodbe]

Failing Test(s)

Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.AbortedStream_ResetsAndDrainsRequest_RefusesFramesAfterEndOfStream
Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.StopProcessingNextRequestSendsGracefulGOAWAYThenFinalGOAWAYWhenAllStreamsComplete
Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.AbortSendsFinalGOAWAY
Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.GOAWAY_Received_ConnectionLifetimeNotification_Cancelled

Error Message

Assert.Equal() Failure: Values differ
Expected: InvalidStreamId
Actual:   FrameAfterStreamClose

Stacktrace

Stack trace

at Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2TestBase.AssertConnectionEndReason(ConnectionEndReason expectedEndReason) in /_/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2TestBase.cs:line 435
at Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.AbortedStream_ResetsAndDrainsRequest_RefusesFramesAfterEndOfStream(Int32 intFinalFrameType) in /_/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2ConnectionTests.cs:line 5913
--- End of stack trace from previous location ---

Logs

Console log

[xUnit.net 00:00:48.04]     Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.AbortedStream_ResetsAndDrainsRequest_RefusesFramesAfterEndOfStream(intFinalFrameType: 9) [FAIL]
[xUnit.net 00:00:48.04]       Assert.Equal() Failure: Values differ
[xUnit.net 00:00:48.04]       Expected: InvalidStreamId
[xUnit.net 00:00:48.04]       Actual:   FrameAfterStreamClose
[xUnit.net 00:00:48.04]       Stack Trace:
[xUnit.net 00:00:48.05]         /_/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2TestBase.cs(435,0): at Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2TestBase.AssertConnectionEndReason(ConnectionEndReason expectedEndReason)
[xUnit.net 00:00:48.05]         /_/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2ConnectionTests.cs(5913,0): at Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.AbortedStream_ResetsAndDrainsRequest_RefusesFramesAfterEndOfStream(Int32 intFinalFrameType)
[xUnit.net 00:00:48.05]       Output:
[xUnit.net 00:00:48.05]         | [0.031s] TestLifetime Information: Starting test AbortedStream_ResetsAndDrainsRequest_RefusesFramesAfterEndOfStream-9 at 2026-03-27T11:13:57
[xUnit.net 00:00:48.05]         | [0.051s] Microsoft.AspNetCore.Server.Kestrel.Http2 Debug: Trace id "TestConnectionId:00000001": HTTP/2 stream error "INTERNAL_ERROR". A Reset is being sent to the stream.
[xUnit.net 00:00:48.05]         | Microsoft.AspNetCore.Connections.ConnectionAbortedException: The connection was aborted by the application.
[xUnit.net 00:00:48.05]         | [0.059s] Microsoft.AspNetCore.Server.Kestrel.Http2 Debug: Connection id "TestConnectionId": HTTP/2 connection error.
[xUnit.net 00:00:48.05]         | Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http2.Http2ConnectionErrorException: HTTP/2 connection error (STREAM_CLOSED): The client sent a HEADERS frame to stream ID 1 which is in the "half-closed (remote) state".

Build

https://dev.azure.com/dnceng-public/public/_build/results?buildId=1354642

[wtgodbe]

The test AbortedStream_ResetsAndDrainsRequest_RefusesFramesAfterEndOfStream expects ConnectionEndReason.InvalidStreamId but gets ConnectionEndReason.FrameAfterStreamClose. Both are error conditions for sending frames after a stream has been reset, but the exact error code depends on the timing of when the RST_STREAM is processed relative to subsequent frames. The race between stream reset processing and frame reception means different error paths can be taken depending on timing, resulting in different ConnectionEndReason values.

The other three tests (StopProcessingNextRequestSendsGracefulGOAWAYThenFinalGOAWAYWhenAllStreamsComplete, AbortSendsFinalGOAWAY, GOAWAY_Received_ConnectionLifetimeNotification_Cancelled) are similarly sensitive to HTTP/2 connection lifecycle timing. These are inherently racy due to the asynchronous nature of HTTP/2 connection management.

[github-actions]

Triage Summary

Area: area-networking — Failing tests are in Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests, which is part of the Kestrel HTTP/2 server implementation.
Type: test-failure (already labeled) — CI test failure report with specific assertion mismatches (InvalidStreamId vs FrameAfterStreamClose) in HTTP/2 connection handling tests.

Potential Duplicates

• None found — Searches for similar Kestrel HTTP/2 GOAWAY / quarantine test failures did not surface exact duplicates for these specific test methods.

Notes

• Four tests are failing, all related to HTTP/2 connection lifecycle (GOAWAY frames, stream abort/drain, connection lifetime notifications).
• The error indicates an unexpected ConnectionEndReason: FrameAfterStreamClose was received instead of InvalidStreamId, suggesting a race condition or ordering issue in HTTP/2 stream state management.
• Linked CI build: (dev.azure.com/redacted)

Generated by Issue Triage Agent for dotnet/aspnetcore for issue #66037 · ◷