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 2019/05/21 17:39:00 UTC
[jira] [Commented] (ARROW-5390) [CI] Job time limit exceeded on
Travis
[ https://issues.apache.org/jira/browse/ARROW-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845074#comment-16845074 ]
Wes McKinney commented on ARROW-5390:
-------------------------------------
I would be inclined to stop testing Python 2.7 in Travis CI right now and instead test it in a docker-compose job. We're getting closer to the Python 2.7 drop dead date so the number of times we may need to fix 2.7-specific issues is growing limited
> [CI] Job time limit exceeded on Travis
> --------------------------------------
>
> Key: ARROW-5390
> URL: https://issues.apache.org/jira/browse/ARROW-5390
> Project: Apache Arrow
> Issue Type: Bug
> Components: Continuous Integration, Python
> Reporter: Antoine Pitrou
> Priority: Major
>
> We now frequently hit the 50 minutes job time limit on Travis-CI on the "Python 2.7 and 3.6 unit tests w/ Valgrind, conda-forge toolchain, coverage" job.
> e.g. https://travis-ci.org/pitrou/arrow/jobs/535373888
> Hopefully we can soon ditch Python 2.7, which would allow saving a bit of time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)