System.Diagnostics.Process.Tests failure on net10.0-linux-Debug-arm64-Mono_Minijit_Debug

[am11]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=893020
Build error leg or test failing: System.Diagnostics.Tests.ProcessTests.TestGetProcessById
Pull request: #110198

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": ["Expected: \".NET Long Runni\"","System.Diagnostics.Tests.ProcessTests.TestGetProcessById"],
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=893020
Error message validated: [Expected: ".NET Long Runni" System.Diagnostics.Tests.ProcessTests.TestGetProcessById]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 12/12/2024 6:55:46 PM UTC

Report

Build	Definition	Test	Pull Request
893020	dotnet/runtime	System.Diagnostics.Tests.ProcessTests.TestGetProcessById	#110631

Summary

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

Report

Build	Definition	Test	Pull Request
893020	dotnet/runtime	System.Diagnostics.Tests.ProcessTests.TestGetProcessById	#110631

Summary

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

[jkotas]

Expected: ".NET Long Runni" is very generic pattern that can match number of unrelated issues. I have updated it to be make it more specific.

[mdh1418]

This looks like a dupe of #107821. It seems odd that the expected name is ".NET Long Runni", do we really expect the process started by CreateDefaultProcess to have that name (which looks like that name stems from a long running task being trimmed

runtime/src/libraries/System.Private.CoreLib/src/System/Threading/Tasks/ThreadPoolTaskScheduler.cs

Line 51 in 1d69684

Name = ".NET Long Running Task"

) instead of dotnet?

All other instances of .NET Long Runni in other issues seem to be some problem with hangs/futex-internal.c when looking at callstacks in #92070, #90019, #105808, and maybe even #109630 and #106595 might have the same underlying issue.

[dotnet-policy-service]

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