[ci-scan] Test failure: CompatibleWithTest_TypeLoadException on Apple mobile CoreCLR

Abierto
  • ¿Algo no está bien?
#137,140 2 comentarios 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
testing

Línea de trabajo

Start with the failing test at Loader/classloader/MethodImpl/CovariantReturns/UnitTest/CompatibleWithTest_TypeLoadException/CompatibleWithTest_TypeLoadException.dll and the linked source console. Trace why the D2 call succeeds on tvOS and iOS simulator despite the invalid covariant override, then compare the affected platform behavior. Done means the test produces its expected TypeLoadException on both affected legs and passes; the issue does not identify the runtime code path responsible.

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

Descripción

agentic-workflows area-VM-coreclr blocking-clean-ci Known Build Error os-ios untriaged

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1667020
Build error leg or test failing: tvos-arm64 Release AllSubsets_CoreCLR_RuntimeTests-Loader/classloader/MethodImpl/CovariantReturns/UnitTest/CompatibleWithTest_TypeLoadException/CompatibleWithTest_TypeLoadException.dll
Pipeline: runtime-extra-platforms, definition 154, main.
Also affected: iossimulator-arm64 Release AllSubsets_CoreCLR_RuntimeTests.
Queues: osx.15.amd64.appletv.open and osx.26.arm64.open.
First build it occurred (earliest verified observation, not an established introducing build): 1653767, finished 2026-10-29T09:48:20.7818427Z.
Source build finished: 2026-11-06T09:02:57.4679438Z.
Follow-up build: 1668850, finished 2026-11-07T07:22:44.0579218Z; the same ordered failure anchors reproduce on both affected legs.

The failure was verified in nine distinct source-and-prior builds: 1653767, 1655451, 1657310, 1658360, 1659071, 1661087, 1663137, 1665174, and 1667020. Ten prior build inventories were inspected. The two older sampled inventories did not expose affected Loader consoles; this is unknown affected-test coverage, not proof of a passing test. The true origin may predate the earliest verified observation. Multiple legs within one build are counted as one occurrence.

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

The D2 case calls a non-overriding method on a type whose base class has an invalid covariant override. It unexpectedly succeeds instead of producing the expected TypeLoadException, and the test returns 101 instead of 100. Other cases print their expected TypeLoadExceptions; those expected exceptions are not the failure signature. No underlying product fix is established by this detection-only scan.

Source console: https://helixr1107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-1d54a7c66c4742b282/Loader/1/console.fec99e9b.log?helixlogtype=result

Run-specific timestamps and application-process prefixes are omitted below. Expected-exception output from the other cases is omitted between the D2 failure and the final assertion:

Running test: Loader/classloader/MethodImpl/CovariantReturns/UnitTest/CompatibleWithTest_TypeLoadException/CompatibleWithTest_TypeLoadException.dll
D2: call non-overriding method MD2 when base class of D2 has invalid covariant override
Unexpectedly succeeded
Test FAILED
Xunit.Sdk.EqualException: Assert.Equal() Failure: Values differ
Expected: 100
Actual:   101
   at Xunit.Assert.Equal[T](T expected, T actual, IEqualityComparer`1 comparer) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/EqualityAsserts.cs:line 73
   at Program.<>c__DisplayClass0_0.<<Main>$>g__TestExecutor41|42(TestFilter filter, StreamWriter tempLogSw, StreamWriter statsCsvSw)
Failed test: Loader/classloader/MethodImpl/CovariantReturns/UnitTest/CompatibleWithTest_TypeLoadException/CompatibleWithTest_TypeLoadException.dll

Error Message

{
  "ErrorMessage": [
    "D2: call non-overriding method MD2 when base class of D2 has invalid covariant override",
    "Unexpectedly succeeded",
    "Actual:   101",
    "Failed test: Loader/classloader/MethodImpl/CovariantReturns/UnitTest/CompatibleWithTest_TypeLoadException/CompatibleWithTest_TypeLoadException.dll"
  ],
  "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

All four literal elements match once, in order, in the saved source Loader console. PASS/SKIP and passed/skipped-test negative checks are empty. The same ordered anchors were verified in both affected source consoles, both follow-up consoles, and 16 consoles from eight distinct prior builds. The D2-specific diagnostic and failed-test marker distinguish this from unrelated assertions in the merged Loader work item.

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

Report
Build Repository Test Pull Request
1670305 dotnet/runtime Main.Main
1669782 dotnet/runtime Main.Main
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 2 2
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.