[ci-scan] Test failure: VectorMath.SinCosDouble asserts "Missing flags on tree" under JitStress2

Abierto
  • ¿Algo no está bien?
#137,175 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
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
compilers

Línea de trabajo

Start with the JIT global morph assertion in src/coreclr/jit/fgdiagnostic.cpp and inspect the scalar fallback named in System.Runtime.Intrinsics.VectorMath for SinCosDouble. Compare the two failing JitStress2 consoles and investigate how the tree flags are produced or checked. Done means the assertion no longer reproduces and the Windows-x64 Release tensors test passes under JitStress2; the issue does not identify the introducing change or fix.

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

Descripción

agentic-workflows area-CodeGen-coreclr blocking-clean-ci-optional Known Build Error untriaged

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1668984
Build error leg or test failing: windows-x64 Release-System.Numerics.Tensors.Tests
Pipeline: runtime-coreclr libraries-jitstress, definition 138, main.
Queue: windows.amd64.open.rt. Stress mode: DOTNET_JitStress=2.
First build it occurred: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1668984 (finished 2026-11-07; first verified occurrence after ten inspected prior builds).
Follow-up build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1669845 (finished 2026-11-08), same method and assertion.

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 JIT asserts during global morph of the double-precision SinCos scalar fallback while running System.Numerics.Tensors.Tests under JitStress2. The work item exits with -1073740286.

The signature reproduces in two distinct builds, source 1668984 and follow-up 1669845. Windows-x64 tensors consoles from all ten prior builds were inspected, including the JitStress2 variants; none contains this assertion.

PR #137046 merged at 2026-11-06T15:27:33Z and describes stronger GTF_GLOB_REF checking and repairs for intrinsic fallbacks. This assertion reproduces in builds finished after that merge; it is not being filed from a pre-fix source build. The scan does not establish the introducing change or the underlying fix.

Process identifiers, image paths, and the checkout prefix are omitted below:

Missing flags on tree [000100]: ---G------
               [000100] -----------                         *  LCL_VAR   simd16<System.Runtime.Intrinsics.Vector128`1>(DA) V02 loc0
Assertion failed '!"Missing flags on tree"' in 'System.Runtime.Intrinsics.VectorMath:<SinCosDouble>g__ScalarFallback|30_0[System.Runtime.Intrinsics.Vector128`1[double],System.Runtime.Intrinsics.Vector128`1[long]](System.Runtime.Intrinsics.Vector128`1[double]):System.ValueTuple`2[System.Runtime.Intrinsics.Vector128`1[double],System.Runtime.Intrinsics.Vector128`1[double]]' during 'Morph - Global' (IL size 106; hash 0x7f28a011; Instrumented Tier1)
File: src/coreclr/jit/fgdiagnostic.cpp:3644
exit code -1073740286

Error Message

{
  "ErrorMessage": "Assertion failed '!\"Missing flags on tree\"' in 'System.Runtime.Intrinsics.VectorMath:<SinCosDouble>g__ScalarFallback",
  "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 complete literal method-and-assertion anchor matches the saved raw source console and the follow-up console, once each. Negative passing/skipped checks are empty. The native assertion is present in the actual Helix console; it is not inferred from an xUnit summary.

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

Report
Build Repository Test Pull Request
1670559 dotnet/runtime System.Numerics.Tensors.Tests.WorkItemExecution
1669845 dotnet/runtime System.Numerics.Tensors.Tests.WorkItemExecution
1669401 dotnet/runtime System.Numerics.Tensors.Tests.WorkItemExecution
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
1 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.