[
https://issues.apache.org/jira/browse/STORM-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522201#comment-14522201
]
ASF GitHub Bot commented on STORM-803:
--------------------------------------
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/539#issuecomment-97956783
Yes, right. We need INFO log since Storm debug messages are printed out
INFO.
Maybe your approach requires Maven to fail fast (--ff), which I didn't used
it yet.
You can see build 20.1 has storm-kafka test error, but it only prints out
storm-hive logs.
Btw, whatever if it works like a charm, we may want to run tests
continuously, cause we can't retry build for now.
Actually collaborators - committers can retry build at Travis CI UI page,
but it checks permission on github repo. Is it a rule that only asfgit has
write access to github repo.?
> 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)
