[ci-scan] Test failure: NameConfigWithPid Broken pipe on macOS

未关闭
  • 哪里不对？
#136,909 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
22/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp, macos
领域
observability

调研方向

Start with the failing test tracing/eventpipe/config/name_config_with_pid and its NameConfigWithPid.Main entry point, then read the linked Helix console log to see where the pipe writer is flushed. The cause is not established, so first reproduce the broken pipe on macOS, then find out why the writer's peer closes early. Done means the test passes reliably on the macOS x64 leg, or the root cause is documented with a fix.

由索引模型根据 Issue 内容生成。

描述

agentic-workflows area-System.Diagnostics 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: macOS x64 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.
Queue: osx.15.amd64.open.
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 exception and entry-point frame below occur in the same contiguous failing-test stack; this is not a generic network-error or shared-harness match. No underlying cause is established by this scan.

The ordered pair was verified in nine distinct source-and-prior builds: 1646416, 1647811, 1648274, 1648697, 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; absence of this signature from other sampled failed builds is not proof of a product fix or a passing affected leg.

Source console: https://helixr1107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-1edd865f76ca4b4ab2/tracing/1/console.4ecdd31e.log?helixlogtype=result

Running test: tracing/eventpipe/config/name_config_with_pid/name_config_with_pid.cmd
Unhandled exception. System.IO.IOException: Broken pipe
 ---> System.Net.Sockets.SocketException (32): Broken pipe
   at System.Net.Sockets.Socket.Send(ReadOnlySpan`1 buffer, SocketFlags socketFlags) in /_/src/libraries/System.Net.Sockets/src/System/Net/Sockets/Socket.cs:line 1243
   at System.IO.Pipes.PipeStream.WriteCore(ReadOnlySpan`1 buffer) in /_/src/libraries/System.IO.Pipes/src/System/IO/Pipes/PipeStream.Unix.cs:line 293
   --- End of inner exception stack trace ---
   at System.IO.Pipes.PipeStream.WriteCore(ReadOnlySpan`1 buffer) in /_/src/libraries/System.IO.Pipes/src/System/IO/Pipes/PipeStream.Unix.cs:line 299
   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: Broken pipe",
    "   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. The repetition is direct output plus the harness copy, not two independent occurrences. No passing or skipped matches were found. Both ordered elements also match the selected follow-up 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 · ~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/config/name_config_with_pid/name_config_with_pid.cmd
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
1 2 2
主要语言
C#
星标
18.4k
派生
5.8k
平均合并
2 天 14 小时
30 天内合并 PR
585

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

dotnet/runtime 的其他 Issue

查看 dotnet/runtime 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。