Repository navigation
System.Diagnostics.Process.Tests failure on net10.0-linux-Debug-arm64-Mono_Minijit_Debug #110643
Description
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
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
Activity
jkotas commentedon Dec 12, 2024
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 commentedon Dec 16, 2024
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 trimmedruntime/src/libraries/System.Private.CoreLib/src/System/Threading/Tasks/ThreadPoolTaskScheduler.cs
Line 51 in 1d69684
dotnet?All other instances of
.NET Long Runniin 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 commentedon Dec 17, 2024
Tagging subscribers to this area: @dotnet/area-system-diagnostics-process
See info in area-owners.md if you want to be subscribed.
jeffhandley commentedon Jan 16, 2025
Assigned to @adamsitnik for triage
adamsitnik commentedon Jan 23, 2025
Triage: it seems that reading a process name on Linux makes some of our tests flaky (#109630, #110643, #111460).
@jkotas has suggested in #111460 (comment) that we maybe reading it too soon. I am going to try to add a simple retry mechanism to see if it helps.
jeffschwMSFT commentedon May 5, 2025
removing blocking-clean-ci has it has not failed in 30 days
jeffhandley commentedon Jul 20, 2025
Closing as it has continued not to have recent hits
jkotas commentedon Jul 20, 2025
It was hit a few days ago in #117743
Summary
danmoseley commentedon Mar 22, 2026
@mdh1418
Unix or at least Linux has a 15+null limit on process names. this is why we use names like ".NET TP Worker"".NET TP Gate"".NET TP Wait"".NET Timer" ... ".NET Long Running Task" should maybe be ".NET LongR Task" although that is a little less nice for less constrained ppl on Windows