[ci-scan] Test failure: EventPipe stop_session asserts ep_rt_providers_validate_all_disabled on macOS arm64

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

Línea de trabajo

Start with the failing test output and the assertion at src/native/eventpipe/ep.c:895 in stop_session, then inspect the EventPipe session shutdown path and the two linked build logs for macOS arm64. Determine why providers remain enabled when the session stops and reproduce the failure; done means the test completes successfully on the affected leg without weakening or disabling it.

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

Descripción

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

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1663860
Build error leg or test failing: osx-arm64 Release NoDynamicCodeCompiled-System.Diagnostics.Tracing.Tests
Pipeline: runtime-libraries-interpreter, definition 330, main.
Queue: osx.26.arm64.open.
First build it occurred: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1663860 (finished 2026-11-04; first verified occurrence in the sampled window).
Follow-up build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1667701 (finished 2026-11-06), same assertion in the NoDynamicCodeCompiled leg.

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

System.Diagnostics.Tracing.Tests aborts after discovery with an EventPipe assertion in stop_session. The source discovers 32 of 37 test cases, then exits with code 133 without completing the run.

The assertion was verified in two distinct builds, source 1663860 and follow-up 1667701. Ten prior build inventories were inspected. Available earlier NoDynamicCodeCompiled tracing consoles complete without this assertion, including build 1659923 (finished 2026-11-02). Some older console blobs are unavailable; no passing result is inferred from an unavailable blob.

The complete assertion output below omits the per-user checkout prefix and process identifier:

ASSERT FAILED
    Expression: ep_rt_providers_validate_all_disabled ()
    Location:   src/native/eventpipe/ep.c:895
    Function:   stop_session
Trace/BPT trap: 5
exit code 133

The inspected open EventPipe filter-recomputation PR describes keyword/level narrowing while other sessions remain active, not this all-providers-disabled assertion. No underlying fix is established here.

Error Message

{
  "ErrorMessage": [
    "Expression: ep_rt_providers_validate_all_disabled ()",
    "Function:   stop_session"
  ],
  "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

Both literal elements match once, in order, in the saved source console and the follow-up console. Passing/skipped negative checks are empty. The native assertion itself is present in the raw Helix console.

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
3133117 dotnet-runtime System.Diagnostics.Tracing.Tests.WorkItemExecution
1672437 dotnet/runtime System.Diagnostics.Tracing.Tests.WorkItemExecution
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
1 2 2
Lenguaje dominante
C#
Estrellas
18.4k
Forks
5.8k
Merge medio
2 d 19 h
PR fusionados (30 d)
590

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.