[
https://issues.apache.org/jira/browse/ARROW-15259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476112#comment-17476112
]
Liya Fan commented on ARROW-15259:
----------------------------------
Sorry [~el...@ursacomputing.com] I am having some problems running the command
you provided:
{{
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile)
on project arrow-format: Compilation failure -> [Help 1]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile)
on project arrow-plasma: Compilation failure -> [Help 1]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile)
on project arrow-memory-core: Compilation failure -> [Help 1]
}}
However, when I built the project manually, it worked fine.
> [Java] [Benchmarking] Large stdout when running benchmarks
> ----------------------------------------------------------
>
> Key: ARROW-15259
> URL: https://issues.apache.org/jira/browse/ARROW-15259
> Project: Apache Arrow
> Issue Type: Bug
> Components: Benchmarking, Java
> Reporter: Elena Henderson
> Priority: Major
>
> Since ARROW-15058 running the Java benchmarks results in stdout logs that are
> extremely large (we're seeing them at ~14gb). This is disrupting running
> benchmarks on conbench.
> We've temporarily worked around this by disabling stdout logging entirely,
> but this will make debugging issues in the future much harder.
> Is there any way to reduce the volume of stdout logging when running these
> benchmarks?
> cc [~dsusanibara] [~fan_li_ya]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
