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

オープン
  • 何か問題がありますか？
#137,174 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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時間
マージ済み PR（30日）
585

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

dotnet/runtime のほかの issue

dotnet/runtime の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。