apache/hudi

Docker demo/integ-test stdout/stderr output only available on process exit

Open

#14,505 建立於 2025年11月30日

在 GitHub 查看
 (0 留言) (0 反應) (1 負責人)Java (4,823 star) (2,431 fork)batch import
area:testsfrom-jiragood first issuepriority:lowpriority:mediumtype:community-support

描述

This is problematic, if the command hangs for e.g, we don't get any logs to indicate where its hanging at.. Better approach is to use something like Piped{Input|Oupput}Stream to implement a thread that can keep printing stdout and stderr as the command runs..

Relevant classes : ITTestHoodieDemo/ ITTTestBase

JIRA info

貢獻者指南

技術棧
javadocker
領域
testingbackend
議題類型
test
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Java basicsDocker familiarity
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
The issue is that stdout/stderr output from Docker demo/integ test commands is only displayed after the process finishes. This makes debugging hangs difficult. The proposed solution is to use PipedInputStream and PipedOutputStream to implement a thread that continuously reads and prints stdout/stderr as the command runs. The relevant classes are ITTestHoodieDemo and ITTestBase in the test infrastructure. The modifications should be localized to these files.
Docker demo/integ-test stdout/stderr output only available on process exit · apache/hudi#14505 | Good First Issue