[
https://issues.apache.org/jira/browse/STORM-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521906#comment-14521906
]
ASF GitHub Bot commented on STORM-803:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/539#issuecomment-97890019
@HeartSaVioR I agree that some things may be lost when we write the logs
out to a file. That is why I added in the `cat` on failure when compiling, and
the `tail -500` on a test failure. So if everything passed there is no issue,
but if something failed we can get something out, even if it is not everything.
If you want to adjust the amount output on failure I am happy to.
I have also been looking at the clojure test runner, but I am really not
ready to update it yet. In most cases for me I have found this more useful at
finding errors than the WARN has been, but that is just me.
> Cleanup travis-ci build and logs
> --------------------------------
>
> Key: STORM-803
> URL: https://issues.apache.org/jira/browse/STORM-803
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
>
> The travis CI build sets logging to WARN which is not ideal. I would much
> rather see the full logs written to a file, and then we can pick from the
> logs what we want to explicitly output.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
