[ci-scan] Test failure: NameConfigWithPid pipe is being closed on Windows

Abierto
  • ¿Algo no está bien?
#136,910 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
18/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
csharp
Área
testing-qa

Línea de trabajo

The failing test is tracing/eventpipe/config/name_config_with_pid, whose NameConfigWithPid.Main writes through a StreamWriter and fails in WriteLine with a pipe-closed IOException. Read the test source and the linked Helix console log to see which process owns the pipe and when it closes. Reproducing needs a Windows crossgen2 composite run of this test. Done would mean the test passes reliably there, which the issue does not establish is a simple fix.

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

Descripción

agentic-workflows area-Infrastructure blocking-clean-ci Known Build Error untriaged

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1659123
Build error leg or test failing: Windows crossgen2 composite / no-tiered-compilation runtime tests-tracing/eventpipe/config/name_config_with_pid/name_config_with_pid
Pipeline: runtime-coreclr crossgen2 outerloop, definition 134, main.
Impacted OS/architectures: Windows 11 x64 and Windows Server 2016 x86.
Queues: windows.amd64.open.rt and windows.10.amd64.open.rt.
First build it occurred: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1646416 (finished 2026-10-23; earliest verified in the sampled window, not an established introduction).
Follow-up build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1661208 (finished 2026-11-03), identical ordered exception and entry-point stack frame.

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

NameConfigWithPid.Main fails while flushing its pipe writer. The exact exception and entry-point frame below belong to the same contiguous failing-test stack. Child output also reports Stack overflow.; this scan does not establish a common cause with other tests that report stack overflow.

The ordered pair was verified in ten distinct source-and-prior builds: 1646416, 1647811, 1648274, 1648697, 1652131, 1653815, 1655529, 1657378, 1658441, and 1659123, and again in follow-up 1661208. Eleven source-and-prior build inventories were inspected. The true origin may predate 2026-10-23; the other sampled failed build does not establish that the affected test passed.

The same Windows x64 exception and ordered entry-point frame also reproduce in crossgen2-composite gcstress builds 1658528 and 1659304. They are covered by this single matcher rather than a second issue.

Source console: https://helixr18s23ayyejvk1x8qcc.blob.core.windows.net/dotnet-runtime-refs-heads-main-27e986d4a6154c2883/tracing/1/console.94b0a6d5.log?helixlogtype=result

Running test: tracing/eventpipe/config/name_config_with_pid/name_config_with_pid.cmd
Unhandled exception. System.IO.IOException: The pipe is being closed.
   at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
   at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64& fileOffset)
   at System.IO.Strategies.OSFileStreamStrategy.Write(Byte[] buffer, Int32 offset, Int32 count)
   at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
   at System.IO.Strategies.BufferedFileStreamStrategy.Flush(Boolean flushToDisk)
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.IO.StreamWriter.WriteLine(String value)
   at NameConfigWithPid.Main(String[] args)

Error Message

{
  "ErrorMessage": [
    "Unhandled exception. System.IO.IOException: The pipe is being closed.",
    "   at NameConfigWithPid.Main(String[] args)"
  ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}
Agentic workflow metadata (ci-failure-scan)

Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 2 hits in failure.log

Both elements match twice, in order, within the failing test's exception output. Repeated direct/harness output is not counted as another build occurrence. No passing or skipped matches were found. Both ordered elements also match all three affected source consoles and all three selected follow-up consoles, plus the two crossgen2-composite gcstress consoles.

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
1665289 dotnet/runtime OutOfProcessTest.tracing/eventpipe/config/name_config_with_pid/name_config_with_pid.cmd
1663236 dotnet/runtime OutOfProcessTest.tracing/eventpipe/rundownvalidation/rundownvalidation/rundownvalidation.cmd
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 12 h
PR fusionados (30 d)
581

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.