dotnet / dotnet/aspnetcore

Quarantine Http2TimeoutTests.HEADERS_ReceivedWithoutAllCONTINUATIONs_WithinRequestHeadersTimeout_AbortsConnection failing intermittently

Open
#65,854 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 10h
Merged PRs (30d)
281

Description

## Failing Test(s)

`Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2TimeoutTests.HEADERS_ReceivedWithoutAllCONTINUATIONs_WithinRequestHeadersTimeout_AbortsConnection`

## Error Message

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

Performed invocations:
Mock(IKestrelTrace:1) (h):
No invocations performed.
```

## Stacktrace

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

Performed invocations:
Mock(IKestrelTrace:1) (h):
No invocations performed.
at Moq.Mock.Verify(Expression`1 expression, Times times, String failMessage)
at Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2TimeoutTests.HEADERS_ReceivedWithoutAllCONTINUATIONs_WithinRequestHeadersTimeout_AbortsConnection()
```

## Logs

```text
See build logs for detailed output. The test verifies that a timeout is triggered when CONTINUATION frames are not received within the request headers timeout period, but the mock verification fails intermittently.
```

## Build

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

> Generated by [Daily Test Quarantine Management](https://github.com/dotnet/aspnetcore/actions/runs/23270202784) · [◷](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

Search the repository for Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2TimeoutTests.HEADERS_ReceivedWithoutAllCONTINUATIONs_WithinRequestHeadersTimeout_AbortsConnection and inspect the related test-quarantine conventions. Review the linked build logs to confirm the intermittent failure, then quarantine the test and verify that the quarantine is recorded for this test.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
networking, testing
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.