[Java] Enable allocator logging in CI
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
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.*
Contributor guide
Research direction
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.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100