[ci-scan] Build break: Apple x64 NativeAOT apps cannot link CryptoKit SHA3 symbols

未关闭
#137,150 7 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@agocke 已经在做这个了。

开始于 2026年11月9日。

  • #137222 来自 @agocke —— 未关闭

评估

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

调研方向

Start with the failing iOS-simulator-x64 and MacCatalyst-x64 NativeAOT build logs linked in the issue, then trace the CryptoKit SHA3 references in libSystem.Security.Cryptography.Native.Apple.a and the Apple NativeAOT build path. Confirm the linker failure on an affected build and identify why the x86_64 SHA3 symbols are missing; done when both affected legs link successfully.

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

描述

agentic-workflows area-System.Security blocking-clean-ci Known Build Error os-macos untriaged

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1668850
Build error leg or test failing: iossimulator-x64 Release AllSubsets_NativeAOT-AppleHybrid.Tests
Also affected: maccatalyst-x64 Release AllSubsets_NativeAOT, queue osx.15.amd64.open.
Pipeline: runtime-extra-platforms, definition 154, main.
First build it occurred: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1665174 (finished 2026-11-05; earliest verified occurrence in the sampled window, not a proven introducing build).
Follow-up build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1669782 (finished 2026-11-08), same linker diagnostic.

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

Apple NativeAOT test applications fail to link CryptoKit SHA3 symbols from libSystem.Security.Cryptography.Native.Apple.a. In the source build, 172 of 175 iOS-simulator-x64 work items and 173 of 176 MacCatalyst-x64 work items fail with this diagnostic (over 98% of each leg). This is one shared linker failure, not hundreds of independent test failures.

The diagnostic was verified in four distinct builds: 1665174, 1667020, 1668850, and follow-up 1669782. Ten prior completed build monitors were inspected; older inventories without an affected console do not establish a passing affected test.

Representative linker output below omits run-specific paths and MSBuild project suffixes:

error MSB4018:   "nominal type descriptor for CryptoKit.SHA3_256", referenced from:
error MSB4018:       type metadata accessor for CryptoKit.HashedAuthenticationCode<CryptoKit.SHA3_256> in libSystem.Security.Cryptography.Native.Apple.a[2](pal_swiftbindings.o)
error MSB4018:   "nominal type descriptor for CryptoKit.SHA3_384", referenced from:
error MSB4018:   "nominal type descriptor for CryptoKit.SHA3_512", referenced from:
error MSB4018: ld: symbol(s) not found for architecture x86_64
error MSB4018: clang: error: linker command failed with exit code 1 (use -v to see invocation)
error MSB4018: ** BUILD FAILED **
error MSB4018:    at Utils.RunProcess(TaskLoggingHelper logger, String path, String args, IDictionary`2 envVars, String workingDir, Boolean ignoreErrors, Boolean silent, MessageImportance debugMessageImportance)
error MSB4018:    at Xcode.BuildAppBundle(String xcodePrjPath, Boolean optimized, String devTeamProvisioning)
error MSB4018:    at AppleAppBuilderTask.Execute()

Error Message

{
  "ErrorMessage": "\"nominal type descriptor for CryptoKit.SHA3_256\", referenced from:",
  "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

The literal diagnostic matches the saved AppleHybrid.Tests source console and the follow-up console, with no passing or skipped matches. The complete source failure inventory was grouped before selecting this representative.


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
Build Repository Test Pull Request
1670305 dotnet/runtime System.Runtime.Numerics.Tests.WorkItemExecution
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 1 1
主要语言
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 摘要。