Quarantine Http3RequestTests.POST_Bidirectional_LargeData_Cancellation_Error

[github-actions]

Failing Test(s)

• Interop.FunctionalTests.Http3.Http3RequestTests.POST_Bidirectional_LargeData_Cancellation_Error

Failure Frequency

Failed 3 times over the past 30 days.

Error Message

No detailed error message was captured in the injected failure data for this test's most recent failures (only aggregate failure count and Helix job/work item identifiers were available); the assembly-level metadata indicates the failures occurred in Helix work item batch_1--net11.0 (job 0f855002-d38a-4a8e-a191-3a9817fb71da).

Stacktrace

Details

No stack trace was captured in the injected failure data for this test.

Logs

Details

No Helix console log content could be retrieved for this run (log download is not permitted for Part 1 analysis; only the injected aggregate failure data was available).

Build

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

Generated by Daily Test Quarantine Management · auto · 367.4 AIC · ⌖ 10.4 AIC · ⊞ 4.3K · ◷

[github-actions]

This test (parameterized over both HTTP/3 and HTTP/2) has failed 3 times over the past 30 days in the same Helix batch (batch_1--net11.0, job 0f855002-d38a-4a8e-a191-3a9817fb71da). No detailed error/stack information was captured in this run's injected failure data beyond the aggregate failure count, so I cannot pinpoint a root cause from the data available here. The test involves large-body POST cancellation handling over Kestrel's HTTP/2 and HTTP/3 transports, which is an area historically prone to timing-sensitive flakiness (several sibling tests in this file are already quarantined for similar cancellation-related races: issues #52573, #38008, #39985, #35070). Given the failure is not a consistent regression (is_consistent_regression is false), quarantining while awaiting further diagnosis is appropriate.

Quarantining via a follow-up PR.

Generated by Daily Test Quarantine Management · auto · 367.4 AIC · ⌖ 10.4 AIC · ⊞ 4.3K · ◷