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
{{ message }}
Repository navigation
[ci-scan] Test failure: GC/API/GC/Collect_Aggressive_LargePages heap commit fails (0x8007000E) #134293
First build it occurred: consistently observed across the scanned window; the GC work item fails on Collect_Aggressive_LargePages in every sampled runtime-coreclr libraries-pgo (definition 145) build from 2026-09-13 through 2026-09-17 (builds 1594615, 1597496, 1600900) and reproduces in follow-up build 1600900 across multiple OS/arch legs. Persistent across the entire scanned window; true origin may predate 2026-09-13.
KBE authoring guidance (ci-failure-scan)
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
GC/API/GC/Collect_Aggressive_LargePages fails during CoreCLR startup — the GC cannot commit its 3 GB region (error 0x8007000E, E_OUTOFMEMORY), so coreclr_initialize fails and the test returns 255 instead of 100. It fails on every GCStandAlone / GCStandAloneServer leg (linux/windows, x64/arm64):
14:12:55.346 Running test: GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd
GC: Committing 3221225472 bytes for a region failed
GC heap initialization failed with error 0x8007000E
BEGIN: coreclr_initialize failed - Error: 0x8007000e
END: coreclr_initialize failed - Error: 0x8007000e
Return code: 1
...
Expected: 100
Actual: 255
END EXECUTION - FAILED
Xunit.Sdk.TrueException: GC: Committing 3221225472 bytes for a region failed
at Xunit.Assert.True(Nullable`1 condition, String userMessage) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 135
14:12:55.684 Failed test: GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd
Error Message
{
"ErrorMessage": [
"Running test: GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd",
"Xunit.Sdk.TrueException: GC: Committing 3221225472 bytes for a region failed",
"Failed test: GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd"
],
"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
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
This issue was generated by an AI agent (GitHub Copilot / ci-failure-scan).
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1597496
Build error leg or test failing: coreclr Pri1 Runtime Tests Run GCStandAlone/GCStandAloneServer linux/windows x64/arm64 checked - GC (GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd)
First build it occurred: consistently observed across the scanned window; the
GCwork item fails onCollect_Aggressive_LargePagesin every sampledruntime-coreclr libraries-pgo(definition 145) build from 2026-09-13 through 2026-09-17 (builds 1594615, 1597496, 1600900) and reproduces in follow-up build 1600900 across multiple OS/arch legs. Persistent across the entire scanned window; true origin may predate 2026-09-13.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
GC/API/GC/Collect_Aggressive_LargePagesfails during CoreCLR startup — the GC cannot commit its 3 GB region (error0x8007000E,E_OUTOFMEMORY), socoreclr_initializefails and the test returns 255 instead of 100. It fails on every GCStandAlone / GCStandAloneServer leg (linux/windows, x64/arm64):Error Message
{ "ErrorMessage": [ "Running test: GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd", "Xunit.Sdk.TrueException: GC: Committing 3221225472 bytes for a region failed", "Failed test: GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd" ], "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
Filed by
ci-failure-scan(detection only).ci-failure-fixwalks open[ci-scan]KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.Note
This issue was generated by an AI agent (GitHub Copilot /
ci-failure-scan).Report
Summary