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

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

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.

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

描述

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
主要语言
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 摘要。