Repository navigation
Description
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1659071
Build error leg or test failing: android-x64 Release AllSubsets_CoreCLR-System.Diagnostics.Process.Tests / System.Diagnostics.Tests.MobileProcessTests.Process_Start_WithStandardHandles_CanRedirectIO
Also affected: android-x64 Release NativeAOT.
Pipeline: runtime-extra-platforms, definition 154, main.
First build it occurred: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1646363 (finished 2026-10-23; earliest verified occurrence in the sampled window, not the established introduction).
Follow-up build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1661087 (finished 2026-11-03), same failure on both runtime variants.
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.- Build Analysis parses only the single JSON block under
Error Message. ErrorMessageis a case-sensitive ordinalString.Containssubstring copied verbatim from the failing log.- Set
BuildRetrytotrueonly for a clear infrastructure retry case.ExcludeConsoleLogdisables Helix console-log scanning.
Error Details
With restrictHandles: True, the child process returns 159 instead of 0. The sibling unrestricted-handles case passes. No root cause is established by this scan.
The signature was verified in eight distinct source-and-prior builds: 1646363, 1648254, 1648681, 1653767, 1655451, 1657310, 1658360, and 1659071. It also reproduces in follow-up build 1661087. Twelve recent builds were inspected; missing Android submissions in other sampled builds do not establish that the test passed or that this regression began in this window. The true origin may predate 2026-10-23.
Log prefixes are omitted below:
[FAIL] System.Diagnostics.Tests.MobileProcessTests.Process_Start_WithStandardHandles_CanRedirectIO(restrictHandles: True)
Assert.Equal() Failure: Values differ
Expected: 0
Actual: 159
at System.Diagnostics.Tests.MobileProcessTests.Process_Start_WithStandardHandles_CanRedirectIO(Boolean restrictHandles)
at System.Reflection.InstanceCalliHelper.Call( fn, Object o, Boolean arg1)
at System.Reflection.IntrinsicInvokeHelper.Instance_Void_Bool(IntPtr fn, Object obj, IntPtr* args, RuntimeType _)
at System.Reflection.IntrinsicInvokeHelper.Invoke(InvokeState& state, InvokerStrategy& strategy, InvokeFunc_RefArgs& invokeFunc, MethodBase method, RuntimeType[] argumentTypes, Object obj, IntPtr* args, Boolean backwardsCompat)
at System.Reflection.MethodBaseInvoker.InvokeWithSharedThunk(Object obj, IntPtr* args)
at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)
Error Message
{
"ErrorMessage": [
"[FAIL] System.Diagnostics.Tests.MobileProcessTests.Process_Start_WithStandardHandles_CanRedirectIO(restrictHandles: True)",
"Assert.Equal() Failure: Values differ",
"Expected: 0",
"Actual: 159"
],
"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
The four elements occur in order in the failing test's own output. Positive counts are 1, 2, 2, and 2, respectively. The failure marker and diagnostic do not match passing or skipped output.
Filed by ci-failure-scan (detection only). ci-failure-fix walks open [ci-scan] KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.
Note
Generated by GitHub Copilot.
Generated by CI Outer-Loop Failure Scanner · copilot · gpt61 · ~907 AIC · ⌖ ~13 AIC · ⊞ 33.3K · ◷
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 3 | 11 | 11 |
Activity
dotnet-policy-service commentedon Nov 3, 2026
Tagging subscribers to this area: @dotnet/area-system-diagnostics-process
See info in area-owners.md if you want to be subscribed.