You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error Details is 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.
ErrorMessage is a case-sensitive ordinal String.Contains substring copied verbatim from the failing log.
Set BuildRetry to true only for a clear infrastructure retry case. ExcludeConsoleLog disables Helix console-log scanning.
Error Details
Testing OOM with small allocations...
Subprocess timed out after 60 seconds.
Expected: 100
Actual: -1
The out-of-process OOM subprocess hangs instead of throwing OutOfMemoryException. Likely the same underlying behavior as #129135 (osx x64); this occurrence is Windows x86. The PR's change is FEATURE_PORTABLE_ENTRYPOINTS-only (browser Wasm), so it is unrelated.
Error Message
{
"ErrorMessage": ["Testing OOM with small allocations...", "Subprocess timed out after 60 seconds."],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": true
}
Agentic workflow metadata (ci-failure-scan)
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hit per signature line in failure.log
Note
This issue was drafted with GitHub Copilot.
Known issue validation
Build: 🔎https://dev.azure.com/dnceng-public/public/_build/results?buildId=1612477 Error message validated:[Testing OOM with small allocations... Subprocess timed out after 60 seconds.] Result validation: ✅ Known issue matched with the provided build. Validation performed at: 9/25/2026 9:24:05 PM UTC
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1612477
Build error leg or test failing: coreclr windows x86 Checked no_tiered_compilation @ Windows.10.Amd64.Open-baseservices/exceptions/OutOfMemoryException/OutOfMemoryException/OutOfMemoryException.cmd
Pull request: #134606
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 out-of-process OOM subprocess hangs instead of throwing
OutOfMemoryException. Likely the same underlying behavior as #129135 (osx x64); this occurrence is Windows x86. The PR's change isFEATURE_PORTABLE_ENTRYPOINTS-only (browser Wasm), so it is unrelated.Error Message
{ "ErrorMessage": ["Testing OOM with small allocations...", "Subprocess timed out after 60 seconds."], "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": true }Agentic workflow metadata (ci-failure-scan)
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hit per signature line in failure.log
Note
This issue was drafted with GitHub Copilot.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1612477
Error message validated:
[Testing OOM with small allocations... Subprocess timed out after 60 seconds.]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/25/2026 9:24:05 PM UTC
Report
Summary