[
https://issues.apache.org/jira/browse/PARQUET-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400212#comment-17400212
]
ASF GitHub Bot commented on PARQUET-2076:
-----------------------------------------
martin-g commented on pull request #924:
URL: https://github.com/apache/parquet-mr/pull/924#issuecomment-900073269
Looking at the [Build
History](https://app.travis-ci.com/github/apache/parquet-mr/builds) I see many
builds which take 30, 40, 50 mins per job.
The shortest workflow (includes 3 jobs) is 50 mins, while the longest one is
almost 2 hours.
The build time depends on how loaded Travis is.
I have added 'travis_wait` because builds were failing for the reasons
explained above !
Looking at the build history I think you can try to reduce it to 30 mins.
But anything less would lead to forcefully stopped jobs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Improve Travis CI build Performance
> -----------------------------------
>
> Key: PARQUET-2076
> URL: https://issues.apache.org/jira/browse/PARQUET-2076
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-mr
> Reporter: Chen Zhang
> Priority: Trivial
>
> According to [Common Build Problems - Travis CI
> (travis-ci.com)|https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received],
> we should carefully use travis_wait, as it may make the build unstable and
> extend the build time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
