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

Abierto
  • ¿Algo no está bien?
#136,907 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
15/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
csharp
Área
compilers, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
C#
Estrellas
18.4k
Forks
5.8k
Merge medio
2 d 14 h
PR fusionados (30 d)
585

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de dotnet/runtime

Todos los issues de dotnet/runtime

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.