[ci-scan] Test failure: Runtime_133715.TestEntryPoint on Mono mini full AOT

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
15/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
csharp
领域
compilers, testing

调研方向

Start with the Helix console log linked in the issue, then find Runtime_133715.Test<Int32>() and TestEntryPoint() in the test sources. Check the report comment for dotnet/runtime#136566 before starting, since a fix may already be under way. Done means explaining why the NullReferenceException is not thrown under the Mono mini full-AOT leg and getting the owners' agreement on the fix.

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

描述

agentic-workflows area-VM-meta-mono blocking-clean-ci Known Build Error untriaged

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1659071
Build error leg or test failing: linux-x64 Release AllSubsets_Mono_MiniFullAot_RuntimeTests minifullaot-Regression_ro_2 / Runtime_133715.TestEntryPoint
Queue: azurelinux.3.amd64.open.rt.
Pipeline: runtime-extra-platforms, definition 154, main.
First build it occurred: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1655451 (finished 2026-10-30; first observed after the preceding sampled build).
Follow-up build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1661087 (finished 2026-11-03), same exception mismatch.

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

Runtime_133715.Test<Int32>() does not throw the expected NullReferenceException on the Mono mini-full-AOT leg. This is a managed test assertion failure despite the merged work item's process exit code being zero.

Twelve recent build monitors were inspected. The exact exception and method frame were verified in four distinct source-and-prior builds: 1655451, 1657310, 1658360, and 1659071, and again in follow-up 1661087. The preceding sampled build 1653767 (finished 2026-10-29) reports the same mini-full-AOT Helix job successful, with all 75 work items passing. This identifies the first observed failure in that sampled sequence, not a proven introducing commit.

Source console: https://helixr1107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-heads-main-8ead3ed96e8a4bf682/Regression_ro_2/1/console.9d1e349d.log?helixlogtype=result

Running test: global::Runtime_133715.TestEntryPoint()
Xunit.Sdk.ThrowsException: Assert.Throws() Failure: No exception was thrown
Expected: typeof(System.NullReferenceException)
   at Xunit.Assert.ThrowsImpl(Type exceptionType, Exception exception, Func`2 inspector) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/ExceptionAsserts.cs:line 524
   at Xunit.Assert.Throws[NullReferenceException](Func`1 testCode)
   at Runtime_133715.Test[Int32]()
   at Runtime_133715.TestEntryPoint()
   at Program.<<Main>$>g__TestExecutor136|0_137(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)
Failed test: global::Runtime_133715.TestEntryPoint()

No product fix or test exclusion is proposed by this detection-only issue.

Error Message

{
  "ErrorMessage": [
    "Xunit.Sdk.ThrowsException: Assert.Throws() Failure: No exception was thrown",
    "Expected: typeof(System.NullReferenceException)",
    "at Runtime_133715.Test[Int32]()",
    "Failed test: global::Runtime_133715.TestEntryPoint()"
  ],
  "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

Each array element has one positive match, in order, within the failing test's own output. No element matches a passing or skipped line.

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 · ~907 AIC · ⌖ ~13 AIC · ⊞ 33.3K · ◷

Report
Build Repository Test Pull Request
1665174 dotnet/runtime Runtime_133715.TestEntryPoint
1663137 dotnet/runtime Runtime_133715.TestEntryPoint
1661660 dotnet/runtime Runtime_133715.TestEntryPoint dotnet/runtime#136566
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 3 3
主要语言
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 摘要。