[
https://issues.apache.org/jira/browse/PARQUET-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473862#comment-16473862
]
ASF GitHub Bot commented on PARQUET-1296:
-----------------------------------------
xhochy commented on issue #476: PARQUET-1296: Travis kills build after 10
minutes, because "no output…
URL: https://github.com/apache/parquet-mr/pull/476#issuecomment-388722823
> Why do we log to a file to print out its content when the execution fails?
Travis captures the output, so I don't think we need to store the logs as a
file.
Having an enormous log is quite annoying when looking for a problem in
another part of the job. Basically it makes the Travis UI unusable and you need
to resort to downloading the log and use grep on your machine. Only printing
parts of the log helped me in other projects to more quickly find the problem
and give appropriate feedback on PRs than. If you do a lot of review, this is
quite a significant time saver.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Travis kills build after 10 minutes, because "no output was received"
> ---------------------------------------------------------------------
>
> Key: PARQUET-1296
> URL: https://issues.apache.org/jira/browse/PARQUET-1296
> Project: Parquet
> Issue Type: Bug
> Affects Versions: 1.8.2
> Reporter: Nandor Kollar
> Priority: Major
>
> {{mvn install --batch-mode -DskipTests=true -Dmaven.javadoc.skip=true
> -Dsource.skip=true > mvn_install.log || (cat mvn_install.log && false)}}
> could take more than 10 minutes, and Travis
> [kills|https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received]
> the build in this case, since no output is produced (it is redirected to the
> log file)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)