[Java] Enable allocator logging in CI
- Langage dominant
- Java
- Étoiles
- 94
- Forks
- 152
- Merge moyen
- 3 j 16 h
- PR mergées (30 j)
- 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.*
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- ci-cd, testing
- Type d'issue
- Fonctionnalité
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100