[Java] Enable allocator logging in CI
- Lingua principale
- Java
- Stelle
- 94
- Fork
- 152
- Merge medio
- 3g 16h
- PR unite (30g)
- 11
Descrizione
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.*
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- ci-cd, testing
- Tipo di issue
- Funzionalità
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100