You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Francois Saint-Jacques (JIRA)" <ji...@apache.org> on 2018/12/10 15:00:00 UTC
[jira] [Commented] (ARROW-2266) [CI] Improve runtime of integration
tests in Travis CI
[ https://issues.apache.org/jira/browse/ARROW-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16714843#comment-16714843 ]
Francois Saint-Jacques commented on ARROW-2266:
-----------------------------------------------
Would it make sense to bundle a docker image with dependencies already installed (cpp toolchain + conda?)
> [CI] Improve runtime of integration tests in Travis CI
> ------------------------------------------------------
>
> Key: ARROW-2266
> URL: https://issues.apache.org/jira/browse/ARROW-2266
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Continuous Integration, Integration
> Reporter: Wes McKinney
> Priority: Major
>
> I was surprised to see that travis_script_integration.sh is taking over 25 minutes to run (https://travis-ci.org/apache/arrow/jobs/349493491). My only real guess about what's going on is that JVM startup time on these hosts is super slow.
> I can think of some things we could do to make things better:
> * Add debugging output so we can see what's slow
> * Write a Java integration test handler that validates multiple files at once
> * Generate a single set of binary files for each producer rather than regenerating them each time (so Java would only need to produce binary files once instead of 3 times like now)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)