Quarantine Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.RequestHeaderStringReuse_MultipleStreams_KnownHea [Content truncated due to length]

[github-actions]

Failing Test(s)

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

Error Message

Xunit.Sdk.EqualException: Assert.Equal() Failure: Values differ
Expected: 1
Actual:   0

Stacktrace

Details

Xunit.Sdk.EqualException: Assert.Equal() Failure: Values differ
Expected: 1
Actual:   0
   at Xunit.Assert.Equal[T](T expected, T actual, IEqualityComparer`1 comparer) in /_/src/xunit.assert/Asserts/EqualityAsserts.cs:line 154
   at Xunit.Assert.Equal[T](T expected, T actual) in /_/src/xunit.assert/Asserts/EqualityAsserts.cs:line 89
   at Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.RequestHeaderStringReuse_MultipleStreams_KnownHeaderReused() in /_/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2ConnectionTests.cs:line 195

Logs

Details

[0.003s] [TestLifetime] [Information] Starting test RequestHeaderStringReuse_MultipleStreams_KnownHeaderReused at 2026-03-23T09:44:28
[0.010s] [Microsoft.AspNetCore.Server.Kestrel.Http2] [Verbose] Connection id "TestConnectionId" sending SETTINGS frame for stream ID 0 with length 24 and flags NONE.
[0.010s] [Microsoft.AspNetCore.Server.Kestrel.Http2] [Verbose] Connection id "TestConnectionId" sending WINDOW_UPDATE frame for stream ID 0 with length 4 and flags 0x0.
[0.010s] [Microsoft.AspNetCore.Server.Kestrel.Http2] [Verbose] Connection id "TestConnectionId" received SETTINGS frame for stream ID 0 with length 6 and flags NONE.
[0.010s] [Microsoft.AspNetCore.Server.Kestrel.Http2] [Verbose] Connection id "TestConnectionId" sending SETTINGS frame for stream ID 0 with length 0 and flags ACK.
[0.012s] [Microsoft.AspNetCore.Server.Kestrel.Http2] [Verbose] Connection id "TestConnectionId" received HEADERS frame for stream ID 1 with length 89 and flags END_STREAM, END_HEADERS.
[0.012s] [Microsoft.AspNetCore.Server.Kestrel.Http2] [Verbose] Connection id "TestConnectionId" sending HEADERS frame for stream ID 1 with length 36 and flags END_STREAM, END_HEADERS.
[0.016s] [Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests] [Error] Test threw an exception.
Xunit.Sdk.EqualException: Assert.Equal() Failure: Values differ
Expected: 1
Actual:   0
   at Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.RequestHeaderStringReuse_MultipleStreams_KnownHeaderReused() in /_/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2ConnectionTests.cs:line 195
[0.018s] [Microsoft.AspNetCore.Server.Kestrel.Http2] [Debug] Connection id "TestConnectionId" is closed. The last processed stream ID was 1.
[0.021s] [TestLifetime] [Information] Finished test RequestHeaderStringReuse_MultipleStreams_KnownHeaderReused in 0.0177378s

Build

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

Generated by Daily Test Quarantine Management · ◷

[github-actions]

Investigation

The test asserts that the ContentType header string is reused (interned) when the same value is sent on multiple HTTP/2 streams:

Assert.Equal(1, requestHeaders.Where(h => h.Name == "content-type").Select(h => h.Value).Distinct().Count());

Expected: 1 (one unique string instance) vs Actual: 0 (no content-type header was found in the collected headers).

Root cause: This is a race condition or ordering issue in the HTTP/2 frame processing pipeline. The test sends two HEADERS frames on streams 1 and 3 and expects both requests to have been processed before it inspects the collected header values. When Actual: 0, it means the second stream's headers were not yet captured in the requestHeaders collection when the assertion ran.

The test uses in-memory HTTP/2 without explicit synchronization to wait for both streams' request headers to be fully processed. Under load or on slower CI machines, the second request's header processing may lag behind the assertion.

Suggested fix: Add explicit synchronization (e.g., a semaphore or Task.WhenAll over both request handler completions) before asserting the header reuse count, or increase the timeout on the wait for both streams to have been processed.

Generated by Daily Test Quarantine Management · ◷

[github-actions]

Re-quarantine Investigation

This test was unquarantined on 2026-04-02 (PR #66083) after passing 100% in the quarantine pipeline. However, it immediately started failing again — 4 failures were observed within 24 hours of unquarantining.

Observed Failure Pattern

The test asserts that after processing a request on stream 1 and calling TriggerTick(), the HTTP/2 stream pool should contain exactly 1 entry:

// Stream has been returned to the pool
Assert.Equal(1, _connection.StreamPool.Count);  // line 195

The failure Expected: 1, Actual: 0 indicates the stream was NOT returned to the pool after TriggerTick(). This is a timing-sensitive operation: TriggerTick() is supposed to trigger stream cleanup, but the cleanup appears to not complete before the assertion is reached in some runs.

Likely Root Cause

The underlying flakiness appears to be a race condition in the HTTP/2 stream pool return logic. The TriggerTick() call may not synchronously complete stream pool operations in all code paths. The test assumes synchronous behavior that is environment-dependent.

The fact that this test re-failed within 24 hours of unquarantining strongly suggests the original fix (if any) did not fully resolve the race condition, and the long stretch of passing was due to environmental conditions rather than a permanent fix.

Recommendation

Investigate whether TriggerTick() guarantees that the stream pool is updated synchronously, or whether an await/flush is needed before the assertion. Consider looking at the HTTP/2 stream lifecycle and pool return logic in Http2Connection.cs.

Note

🔒 Integrity filter blocked 47 items

The following items were blocked because they don't meet the GitHub integrity level.

• #66092 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #66084 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #66075 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #66070 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #66061 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #66060 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #66003 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #65930 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #65928 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #65893 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #65891 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #65887 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #65880 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #65871 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #65870 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #65869 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• ... and 31 more items

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Daily Test Quarantine Management · ◷