[
https://issues.apache.org/jira/browse/PARQUET-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400206#comment-17400206
]
ASF GitHub Bot commented on PARQUET-2076:
-----------------------------------------
YunLemon commented on pull request #924:
URL: https://github.com/apache/parquet-mr/pull/924#issuecomment-900068394
I don't think 60 minutes is a good value. Judging from the build of this PR,
the running time of these two commands is less than 10 minutes(116.41s and
658.30s).
If the command gets stuck, then we will wait for 60 minutes?
--
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)
