[ci-scan] Hang: Microsoft.Extensions.Configuration.Functional.Tests times out on MacCatalyst after 4500 seconds

Đang mở
  • Có gì không ổn?
#137,152 1 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, macos
Lĩnh vực
ci-cd, testing

Hướng nghiên cứu

Start with the linked build logs and compare the MacCatalyst CoreCLR and NativeAOT runs for Microsoft.Extensions.Configuration.Functional.Tests. The issue confirms repeated 4500-second timeouts but does not identify a cause or a source file to change. Trace the test launch and XHarness timeout path; done means the tests complete successfully on MacCatalyst without the timeout.

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

Mô tả

agentic-workflows area-Extensions-Configuration blocking-clean-ci Known Build Error untriaged

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1668850
Build error leg or test failing: maccatalyst-arm64 Release AllSubsets_NativeAOT-Microsoft.Extensions.Configuration.Functional.Tests
Also affected: the same assembly on maccatalyst-arm64 Release AllSubsets_CoreCLR.
Queue: osx.26.arm64.open.
Pipeline: runtime-extra-platforms, definition 154, main.
Follow-up build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1669782 (finished 2026-11-08), same 4500-second application timeout.
First build it occurred: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1653767 (finished 2026-10-29; earliest verified 4500-second timeout in the ten-prior-build sample, not a proven introducing build).

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

XHarness times out the configuration functional-test application after 75 minutes on MacCatalyst arm64. It subsequently reports Test run never launched; an earlier harness line says Test execution started, so that final diagnostic alone does not establish whether launch or managed execution is the cause. No underlying fix is established here.

The source and follow-up each contain this timeout on both CoreCLR and NativeAOT. Ten prior completed build monitors were inspected, with additional 4500-second configuration timeouts verified in 1653767, 1655451, 1657310, 1658360, 1659071, 1661087, and 1663137. Multiple runtime variants within a build are counted as one occurrence. The later prior consoles have different failure signatures and are not counted as the same timeout.

Run-specific paths, process identifiers, timestamps, and command prefixes are omitted:

./xharness-helix-job.apple.sh --app Microsoft.Extensions.Configuration.Functional.Tests.app --target maccatalyst --command-timeout 4980 --timeout 01:15:00 --launch-timeout 01:15:00 --includes-test-runner --expected-exit-code 0
info: Preparing run for maccatalyst
 dbug: Test execution started
fail: Run timed out after 4500 seconds
 dbug: error: attach failed: no such process
 dbug: Test run timed out after 75 minute(s).
 dbug: Could not find pid in mtouch output.
 dbug: Test run never launched
warn: Application test run timed out. Use --timeout to adjust the configured timeout.

Error Message

{
  "ErrorMessage": [
    "--app Microsoft.Extensions.Configuration.Functional.Tests.app --target maccatalyst",
    "Run timed out after 4500 seconds"
  ],
  "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

Both literals match once, in order, in the saved source work-item console and the follow-up console. The specific application and target distinguish this from unrelated assembly timeouts or the separate 10800-second runtime-test hang. No element matches passing or skipped output. The unreliable final launch diagnostic is not part of the matcher.

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 · ~347 AIC · ⌖ ~14 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.