dotnet / dotnet/aspnetcore

Quarantine Http3RequestTests.POST_Bidirectional_LargeData_Cancellation_Error

Open
#68,850 1 comment 0 reactions 0 assignees View on GitHub
area-networking test-failure
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 6h
Merged PRs (30d)
290

Description

## 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

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

## Logs

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](https://github.com/dotnet/aspnetcore/actions/runs/33077421295) · auto · 367.4 AIC · ⌖ 10.4 AIC · ⊞ 4.3K · [◷](https://github.com/search?q=repo%3Adotnet%2Faspnetcore+is%3Aissue+%22gh-aw-workflow-call-id%3A+dotnet%2Faspnetcore%2Ftest-quarantine%22&type=issues)

Contributor guide

Open the contributing guide

Research direction

Start with Interop.FunctionalTests.Http3.Http3RequestTests.POST_Bidirectional_LargeData_Cancellation_Error and inspect the linked Azure build for available failure details. The issue provides no stack trace or logs, so investigate how the test fails under net11.0 and establish a reproducible cause; completion requires addressing the cancellation failure and confirming the test is reliable.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
networking, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.