[Java] Enable allocator logging in CI
- 主要語言
- Java
- 星號
- 94
- 分支
- 152
- 平均合併
- 3 天 16 小時
- 30 天內合併 PR
- 11
描述
This would help track down certain flaky tests.
**Reporter**: [David Li](https://issues.apache.org/jira/browse/ARROW-18035) / @lidavidm
#### Related issues:
- [[Java][FlightRPC] TestBasicOperation.getStreamLargeBatch is flaky on Windows CI](https://github.com/apache/arrow-java/issues/236) (relates to)
**Note**: *This issue was originally created as [ARROW-18035](https://issues.apache.org/jira/browse/ARROW-18035). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
貢獻指南
研究方向
Start by locating the Java CI configuration and the TestBasicOperation.getStreamLargeBatch test mentioned in the related issue. Run the affected Windows CI test and inspect how allocator diagnostics are currently emitted. Done means allocator logging is enabled in CI so failures provide the diagnostic output needed to investigate the flake.
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- java
- 領域
- ci-cd, testing
- Issue 類型
- 功能
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100