"...\dotnet.exe" exec --runtimeconfig System.Diagnostics.Process.Tests.runtimeconfig.json --depsfile System.Diagnostics.Process.Tests.deps.json xunit.console.dll System.Diagnostics.Process.Tests.dll -xml testResults.xml -nologo -nocolor -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing
Discovering: System.Diagnostics.Process.Tests (method display = ClassAndMethod, method display options = None)
Discovered: System.Diagnostics.Process.Tests (found 423 of 451 test cases)
Starting: System.Diagnostics.Process.Tests (parallel test collections = on [4 threads], stop on fail = off)
System.Diagnostics.Tests.ProcessStartInfoTests.ShellExecute_Nano_Fails_Start [SKIP]
Condition(s) not met: "IsWindowsNanoServer"
System.Diagnostics.Tests.ProcessTests.NonElevatedUser_QueryProcessNameOfSystemProcess [SKIP]
Condition(s) not met: "IsNotPrivilegedProcess"
Invalid number of parameters
0 File(s) copied
['System.Diagnostics.Process.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]
{
"ErrorMessage": ["Starting: System.Diagnostics.Process.Tests", "['System.Diagnostics.Process.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]"],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1618965
Build error leg or test failing: windows-x86 Debug Libraries_CheckedCoreCLR-System.Diagnostics.Process.Tests
Pull request: #134960
This is a recurrence of #131389 (the same
System.Diagnostics.Process.Testswhole-work-item hang on Windows), which was closed on 2026-09-21 after 30 days without failures. That one was onwindows-x64 Release NativeAOT_Libs; this one is on CoreCLRwindows-x86Checked. Build Analysis reports a 2.61% failure rate for this work item.KBE authoring guidance (ci-failure-scan)
Error Detailsis for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.Error Message.ErrorMessageis a case-sensitive ordinalString.Containssubstring copied verbatim from the failing log.BuildRetrytotrueonly for a clear infrastructure retry case.ExcludeConsoleLogdisables Helix console-log scanning.Error Details
The work item starts and reports a couple of
[SKIP]lines. After that no further output appears, until the Helix executor kills it (exit code -3, about 15m35s). No[FAIL]line is emitted, so the hanging test is not identified.Configuration:
net11.0-windows-Debug-x86-coreclr_checked-Windows.10.Amd64.Open, Helix jobe45775cb-103a-475f-9f07-250ab1a48c98.Error Message
{ "ErrorMessage": ["Starting: System.Diagnostics.Process.Tests", "['System.Diagnostics.Process.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]"], "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": false }Agentic workflow metadata (ci-failure-scan)
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hits in failure.log
Note
This issue was drafted with GitHub Copilot assistance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1618965
Error message validated:
[Starting: System.Diagnostics.Process.Tests ['System.Diagnostics.Process.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 10/1/2026 4:30:43 AM UTC
Report
Summary