[Java] Enable allocator logging in CI
- Linguagem predominante
- Java
- Estrelas
- 94
- Forks
- 152
- Merge médio
- 3d 16h
- PRs com merge (30d)
- 11
Descrição
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.*
Guia de contribuição
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- java
- Domínio
- ci-cd, testing
- Tipo de issue
- Funcionalidade
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 35/100