You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2022/11/29 09:48:00 UTC
[jira] [Commented] (ARROW-13221) [C++] arrow_reader_writer_test.cc slow to compile
[ https://issues.apache.org/jira/browse/ARROW-13221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640576#comment-17640576 ]
Antoine Pitrou commented on ARROW-13221:
----------------------------------------
I think there are two aspects to this:
1) split the tests into a least two different test files
2) rewrite some of the templated tests (inducing long code generation times at compilation) to be runtime-parametric instead (for example using RandomArrayGenerator or ArrayFromJSON)
Given that those tests have grown organically, step 2 above will probably be slightly cumbersome... One needs to understand what each test checks for and rewrite it while keeping its intent.
cc [~kou] [~benpharkins]
> [C++] arrow_reader_writer_test.cc slow to compile
> -------------------------------------------------
>
> Key: ARROW-13221
> URL: https://issues.apache.org/jira/browse/ARROW-13221
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Reporter: Antoine Pitrou
> Priority: Minor
>
> As soon as some optimizations are enabled, {{src/parquet/arrow/arrow_reader_writer_test.cc}} becomes extremely slow to compile (more than one minute just for itself). This is perceivable on e.g. the {{conda-cpp-valgrind}} build where we add {{-Og}} to the gcc flags in order to make the tests less slow under emulation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)