[
https://issues.apache.org/jira/browse/STORM-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518104#comment-14518104
]
ASF GitHub Bot commented on STORM-803:
--------------------------------------
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/539#issuecomment-97212547
LGTM on adding all test reports to print out issues!
Btw, it seems to be regression.
I've thought about logging to file, but if we can't access log file or
can't print part of logs which points to failed build, it isn't informative
anymore.
As we can see, printing "system-out" and "system-err" doesn't work at least
Kafka tests.
Could we upload log file to somewhere?
Travis CI has a plugin which uploads artifact to S3, so we can use it.
Just I don't know about "free storage" and it should be accessed via http
for easy seeing.
> 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)
