Fix dotnet test hang when the test app process exits but a child process of it remains alive#52558
Build #20260211.12 had test failures
Details
- Failed: 12 (0.01%)
- Passed: 119,034 (96.66%)
- Other: 4,103 (3.33%)
- Total: 123,149
Annotations
Check failure on line 1 in Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.1.WorkItemExecution
azure-pipelines / dotnet-sdk-public-ci
Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.1.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
Check failure on line 1 in Microsoft.NET.Build.Tests.dll.14.WorkItemExecution
azure-pipelines / dotnet-sdk-public-ci
Microsoft.NET.Build.Tests.dll.14.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
Check failure on line 1 in Microsoft.NET.Build.Tests.dll.14.WorkItemExecution
azure-pipelines / dotnet-sdk-public-ci
Microsoft.NET.Build.Tests.dll.14.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
Check failure on line 1 in Microsoft.NET.Build.Tests.dll.21.WorkItemExecution
azure-pipelines / dotnet-sdk-public-ci
Microsoft.NET.Build.Tests.dll.21.WorkItemExecution
The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.