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

Đang mở
  • Có gì không ổn?
#137,174 3 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
4/5
Thời gian dự kiến
3-5 ngày
Mức phù hợp với người mới
35/100
Loại issue
Lỗi
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
csharp
Lĩnh vực
operating-systems, testing

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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
Ngôn ngữ chính
C#
Star
18.4k
Fork
5.8k
Merge trung bình
2 ngày 14 giờ
Pull request đã merge (30 ngày)
585

Chuẩn bị môi trường

Mở trong Codespaces

Khởi chạy dev container của dự án ngay trên trình duyệt, bằng tài khoản GitHub của bạn.

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của dotnet/runtime

Tất cả issue của dotnet/runtime

Issue tương tự

Thêm issue về C#

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.