karma-runner/karma

Ensure all stream buffers are drained before exiting process in single run mode.

Open

#742 建立於 2013年9月11日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)JavaScript (11,918 star) (1,703 fork)batch import
help wantedtype: bugwindows

描述

After investigating a strange behavior on running karma with TeamCity on Windows, I noticed the following issue.

When running the following command in PowerShell:

karma start --single-run | Out-File C:\test.out

The writing function is non-blocking/asynchronous & the written/piped data can be buffered, which could lead to some test results being lost.

Karma needs to ensure that all buffers have been drained or that the writing functions have completed (if they are non-blocking) before exiting the process.

貢獻者指南

技術棧
nodejs
領域
backendtestingdeveloper experience
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Node.js streamsasynchronous programming
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Examine the main process exit logic in Karma, likely in lib/server.js or similar. Look for where the process exits after single run. Investigate how stdout/stderr streams are handled and ensure all pending writes are completed before calling process.exit. The issue mentions PowerShell and Out File, but the core problem is generic buffering in Node.js streams.