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

Aperta
  • Qualcosa non va?
#137,175 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
compilers

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
C#
Stelle
18.4k
Fork
5.8k
Merge medio
2g 14h
PR unite (30g)
585

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di dotnet/runtime

Tutte le issue di dotnet/runtime

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.