-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Test Failure] System.Net.Http.WinHttpHandlerFunctional.Tests.WinHttpHandlerTest.SendAsync_SlowServerRespondsAfterDefaultReceiveTimeout_ThrowsHttpRequestException #96481
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/public/_build/results?buildId=510958 Error MessageFill the error message using step by step known issues guidance. {
"ErrorMessage": "System.Net.Http.WinHttpHandlerFunctional.Tests.WinHttpHandlerTest.SendAsync_SlowServerRespondsAfterDefaultReceiveTimeout_ThrowsHttpRequestException [FAIL]",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
|
The known issue does not seem to get matched, but it should IMO. The failure log can be found via
In the DetailsUrl, there is "ConsoleOutputUri": "https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-cfed76aa4fff41c4bd/System.Net.Http.WinHttpHandler.Functional.Tests/3/console.2f0f7f31.log?helixlogtype=result", which contains the failure. @dotnet/dnceng does the Known Issues infrastructure fall under your team? Can you please take a look? If not, do you know who maintains the Known Issues? |
@AlitzelMendez can you take a look at this, please? |
Hi @rzikm, For context, for known issues we review two things:
the first link that you shared for the build doesn't have the error: https://dev.azure.com/dnceng-public/public/_build/results?buildId=511527&view=logs&j=2686528b-6bb9-52cf-c87c-9a2bbdff7996&t=5c32730d-9d2b-5d94-bfff-01026160003a and the second link doesn't seem to be entitled to any test reported to azdo, when I mention test I am referring to the ones in this tab: https://dev.azure.com/dnceng-public/public/_build/results?buildId=511527&view=ms.vss-test-web.build-test-results-tab Additionally if your link is just mentioned in the build log or any log, we don't parse that log looking for links pointing to other logs, we just analyze the log as a text comparing it with the error message. |
The test is
Let's have a look at it from a different perspective. I am monitoring frequently failing tests using the Kusto Querycluster('engsrvprod.kusto.windows.net').database('engineeringdata').AzureDevOpsTests
| where TestName has 'SendAsync_SlowServerRespondsAfterDefaultReceiveTimeout_ThrowsHttpRequestException'
| where Outcome == 'Failed' // or Outcome == 'PassedOnRerun'
| distinct JobId, WorkItemId, Message, StackTrace, TestName, Arguments, Outcome
| join kind=inner (cluster('engsrvprod.kusto.windows.net').database('engineeringdata').Jobs
| where Finished > now(-14d)
| extend TargetBranch = extractjson("$.['System.PullRequest.TargetBranch']", Properties)
| where (Branch == 'refs/heads/main') or (Source startswith "pr/" and TargetBranch == 'main')
| summarize arg_max(JobName=Name, Finished, Properties, Type, Branch, Source, Started, QueueName, Attempt, Build, TargetBranch) by JobId
| project-rename JobType = Type) on JobId
| extend PropertiesJson = parse_json(Properties)
| extend OS = replace_regex(tostring(PropertiesJson.operatingSystem), @'\((.*)\).*|([^\(].*)', @'\1\2')
| extend Runtime = iif(PropertiesJson.runtimeFlavor == "mono", "Mono", iif(PropertiesJson.DefinitionName contains "coreclr", "CoreCLR", ""))
| extend Architecture = PropertiesJson.architecture
| extend DefinitionName = PropertiesJson.DefinitionName
| project-away JobId
| extend BuildId = extractjson("$.['BuildId']", Properties)
| join kind=inner (cluster('engsrvprod.kusto.windows.net').database('engineeringdata').WorkItems
| project-keep ConsoleUri, WorkItemId) on WorkItemId
| project-away PropertiesJson
| project-reorder Started, TestName, ConsoleUri, BuildId, JobName, OS, Architecture, DefinitionName, Branch, TargetBranch, Attempt, Build//, *
; The query returns, among others, failures occuring connected to build 511527 The associated Console output link is https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-cfed76aa4fff41c4bd/System.Net.Http.WinHttpHandler.Functional.Tests/3/console.2f0f7f31.log?helixlogtype=result and the associated failure is indeed mentioned in the output
So my assumption is that if I file a Known Build error against this build and test, it should match correctly. Or am I missing something? |
Triage: this is an Outerloop test that fails quite regularly for 17 failures in the past 30 days (2023-12-06 to 2024-01-05). We need to investigate in 9.0. |
could you please share with me a link to the test in AzDO? as I mentioned it needs to be a test that appears on the AzDO tab, we don't parse the log, so if it is just mentioned and not reported back to AzDO we will not review it we don't pull the test (helix work items) for our kusto tables, we ask AzDO to return all the tests ran in that build, AzDO returns all the test that are on https://dev.azure.com/dnceng-public/public/_build/results?buildId=511527&view=ms.vss-test-web.build-test-results-tab and we analyze those tests, if the test is not in there we won't analyze that log |
I see, AzDO seems to report entire work items as failed and not individual failed tests. I think we have recently run into this similar issue in #95898 (comment). @carlossanlop Could this be the same problem? |
@AlitzelMendez, I have taken another look and it seems to me that the test failure is actually reported in AzDO Can you please take a look? I am also seeing the same in #96689 |
Hi @rzikm, |
removing blocking-clean-ci due to not failing for 30 days
|
The actual exception seems to be
|
Similar error with different reason and error code:
|
I will watch this issue in CI (main) for a while, and if it happens again, I'll re-open. |
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=715461
Build error leg or test failing: System.Net.Http.WinHttpHandlerFunctional.Tests.WinHttpHandlerTest.SendAsync_SlowServerRespondsAfterDefaultReceiveTimeout_ThrowsHttpRequestException
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=715461
Error message validated:
[System.Net.Http.WinHttpHandlerFunctional.Tests.WinHttpHandlerTest.SendAsync_SlowServerRespondsAfterDefaultReceiveTimeout_ThrowsHttpRequestException [FAIL] Error 12152 calling WINHTTP_CALLBACK_STATUS_REQUEST_ERROR
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/25/2024 3:32:56 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: