[ci-scan] Test failure: Collect_Aggressive_LargePages cannot initialize GC on Windows

Aperta
  • Qualcosa non va?
#137,174 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
operating-systems, testing

Direzione di ricerca

Start with the failing test at coreclr Pri1 Runtime Tests Run GCStandAlone, GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd, and compare the Windows x64 and arm64 logs from the listed builds. Investigate why standalone GC cannot commit the 3 GiB region and returns 0x8007000E during initialization. Done means the Windows test initializes and passes on the affected legs without disabling it.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

agentic-workflows area-GC-coreclr blocking-clean-ci Known Build Error untriaged

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1665983
Build error leg or test failing: coreclr Pri1 Runtime Tests Run GCStandAlone windows x64 checked-GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd
Pipeline: gc-standalone, definition 146, main.
Also affected: GCStandAlone Windows arm64. Queues: windows.amd64.open.rt and windows.11.arm64.open.
First build it occurred: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1639544 (finished 2026-10-18; oldest available verified occurrence in the sampled window, not a proven introducing build).
Follow-up build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1669993 (finished 2026-11-08), same initialization failure and exit -1.

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

The non-server standalone-GC Windows leg cannot commit a 3 GiB region for the large-pages test. Runtime initialization fails with 0x8007000E and returns -1 instead of the expected 100. This is not the GCCoop::GCCoop/pThread assertion in the server leg, nor the Linux SIGSEGV manifestation.

The Windows initialization failure was verified in eight prior builds (1639544, 1642124, 1645404, 1648378, 1650785, 1654299, 1658698, 1661878), plus source 1665983 and follow-up 1669993: ten distinct builds. Ten prior inventories were inspected; the two oldest console blobs are unavailable. The true origin may predate 2026-10-18; unavailable blobs are not counted as passing builds.

Related: dotnet/runtime#130302 describes the Linux-x64 initialization/exit-255 manifestation. This issue explicitly covers Windows x64/arm64 and its exit -1 output; the ordered matcher includes that distinction.

GC: Committing 3221225472 bytes for a region failed
GC heap initialization failed with error 0x8007000E
Expected: 100
Actual: -1
END EXECUTION - FAILED
Failed test: GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd

Error Message

{
  "ErrorMessage": [
    "GC: Committing 3221225472 bytes for a region failed",
    "GC heap initialization failed with error 0x8007000E",
    "Actual: -1",
    "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

All four elements match in order in the saved Windows source console and the follow-up console. The final failed-test anchor matches once. Passing/skipped negative checks are empty. The diagnostic is isolated to this test's output in the merged GC console.

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 · ~285 AIC · ⌖ ~15 AIC · ⊞ 33.3K · ◷

Report
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
Lingua principale
C#
Stelle
18.4k
Fork
5.8k
Merge medio
2g 14h
PR unite (30g)
585

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di dotnet/runtime

Tutte le issue di dotnet/runtime

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.