Repository navigation
HttpMetricsTest_Http20.TimeInQueue_RecordedForNewConnectionsOnly test failure #122522
Description
System.Net.Http.Functional.Tests.HttpMetricsTest_Http20.TimeInQueue_RecordedForNewConnectionsOnly [FAIL]
Assert.Equal() Failure: Values differ
Expected: 1
Actual: 2
Stack Trace:
/_/src/libraries/System.Net.Http/tests/FunctionalTests/MetricsTest.cs(907,0): at System.Net.Http.Functional.Tests.HttpMetricsTest.<TimeInQueue_RecordedForNewConnectionsOnly>b__26_0(Uri uri)
/_/src/libraries/Common/tests/System/Threading/Tasks/TaskTimeoutExtensions.cs(120,0): at System.Threading.Tasks.TaskTimeoutExtensions.GetRealException(Task task)
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1230390
Build error leg or test failing: System.Threading.Threads.Tests.ThreadTests.IsBackgroundTest
Pull request: #122513
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorPattern": "HttpMetricsTest.*TimeInQueue_RecordedForNewConnectionsOnly \\[FAIL\\]",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1230390
Error message validated: [HttpMetricsTest_Http20.TimeInQueue_RecordedForNewConnectionsOnly [FAIL] Values differ]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 12/13/2025 9:46:21 AM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 1 | 3 | 3 |
Known issue validation
Build: 🔎
Result validation:
Validation performed at: 9/3/2026 5:13:11 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 1 | 3 | 3 |
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 1 | 6 | 89 |
Activity
dotnet-policy-service commentedon Dec 13, 2025
Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.
SakeTao commentedon Dec 16, 2025
Failed in: runtime-coreclr libraries-jitstress 20251214.1
Failed tests:
Error message:
Stack trace:
ManickaP commentedon Jan 7, 2026
There's tons of re-runs of this as well. We should look into it and fix it. This is likely a test-bug.
michaellinhq commentedon Feb 15, 2026
Hi, I reviewed 'HttpMetricsTest_Http20.TimeInQueue_RecordedForNewConnectionsOnly test failure' and can start immediately. I can deliver a first usable version quickly and iterate based on your feedback. If this scope still matches your priority, I can proceed right away.
kuba1 commentedon Feb 23, 2026
@ManickaP Could you point me to the pipeline this is failing on? Had a bit of a hard time finding it since all the runs mentioned here are deleted.
I didn't manage to reproduce this locally, but dug into the code a little bit and it seems that the
HttpConnectionPoolcannot find an appropriate connection for second (or third?) request, even though the connection should already be established.There is additional logging that can be enabled with
EventListenerthat shows what's happening inside theHttpConnectionPool. I created a draft PR: #124740jeffschwMSFT commentedon Mar 5, 2026
removing blocking-clean-ci has it has not failed in 30 days
ManickaP commentedon Aug 4, 2026
No recent occurrences, but still a lot of PassedOnRerun. Keeping it open, but punting.
svick commentedon Aug 7, 2026
I saw this fail for
HttpMetricsTest_Http30.TimeInQueue_RecordedForNewConnectionsOnlyin https://dev.azure.com/dnceng-public/public/_build/results?buildId=1542869&view=ms.vss-test-web.build-test-results-tab&runId=42480476&resultId=228215&paneView=debug, so I have changed the KBE to match both Http2 and Http3.The log
Synchronize HTTP/2 queue-time test with connection publication (#134423)