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

Abierto
  • ¿Algo no está bien?
#137,174 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
operating-systems, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
C#
Estrellas
18.4k
Forks
5.8k
Merge medio
2 d 14 h
PR fusionados (30 d)
585

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dotnet/runtime

Todos los issues de dotnet/runtime

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.