HttpMetricsTest_Http20.TimeInQueue_RecordedForNewConnectionsOnly test failure

[jkotas]

    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.

{
  "ErrorMessage": ["HttpMetricsTest_Http20.TimeInQueue_RecordedForNewConnectionsOnly [FAIL]","Values differ"],
  "ErrorPattern": "",
  "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
0	0	0

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

[SakeTao]

Failed in: runtime-coreclr libraries-jitstress 20251214.1

Failed tests:

net11.0-linux-Release-x64-jitstress2-AzureLinux.3.Amd64.Open
    - System.Threading.Threads.Tests.ThreadTests.IsBackgroundTest

Error message:

Assert.Throws() Failure: No exception was thrown
Expected: typeof(System.Threading.ThreadStateException)

Stack trace:

   at System.Threading.Threads.Tests.ThreadTests.IsBackgroundTest() in /_/src/libraries/System.Threading.Thread/tests/ThreadTests.cs:line 580
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/coreclr/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.CoreCLR.cs:line 36
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57

[ManickaP]

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]

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]

@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 HttpConnectionPool cannot 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 EventListener that shows what's happening inside the HttpConnectionPool. I created a draft PR: #124740

[jeffschwMSFT]

removing blocking-clean-ci has it has not failed in 30 days

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0