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

未关闭
  • 哪里不对？
#137,174 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp
领域
operating-systems, testing

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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
主要语言
C#
星标
18.4k
派生
5.8k
平均合并
2 天 14 小时
30 天内合并 PR
585

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

dotnet/runtime 的其他 Issue

查看 dotnet/runtime 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。