You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2018/09/10 17:33:00 UTC

[jira] [Updated] (ARROW-2671) [Python] Run ASV suite in nightly build, only run in Travis CI on demand

     [ https://issues.apache.org/jira/browse/ARROW-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wes McKinney updated ARROW-2671:
--------------------------------
    Fix Version/s:     (was: 0.11.0)
                   0.12.0

> [Python] Run ASV suite in nightly build, only run in Travis CI on demand
> ------------------------------------------------------------------------
>
>                 Key: ARROW-2671
>                 URL: https://issues.apache.org/jira/browse/ARROW-2671
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Python
>            Reporter: Wes McKinney
>            Priority: Major
>              Labels: nightly
>             Fix For: 0.12.0
>
>
> Lately the main Travis CI build is running nearly 40 minutes long, e.g. here is the latest commit on master
> https://travis-ci.org/apache/arrow/builds/387326546
> A fair chunk of the long runtime is spent running the Python benchmarks at the end of the test suite. We should absolutely keep these running smoothly. However:
> * It may be just as valuable to run them on master nightly, and report in if they are broken
> * We could add a check to look at the commit message and run them in Travis CI if requested
> If others agree, I suggest that as soon as the packaging bot / nightly build tool is working properly, that we make these changes in the interest of improving CI build times



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)