You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2015/06/05 01:39:39 UTC

[jira] [Updated] (STORM-850) Change storm-core's unit test console log level to WARN when running with Travis CI

     [ https://issues.apache.org/jira/browse/STORM-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jungtaek Lim updated STORM-850:
-------------------------------
    Summary: Change storm-core's unit test console log level to WARN when running with Travis CI  (was: Change storm-core's unit test console log level to WARN)

> Change storm-core's unit test console log level to WARN when running with Travis CI
> -----------------------------------------------------------------------------------
>
>                 Key: STORM-850
>                 URL: https://issues.apache.org/jira/browse/STORM-850
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Jungtaek Lim
>            Assignee: Jungtaek Lim
>
> We adopted Travis CI (STORM-704) , and we had to adjust unit tests log level to WARN when unit tests are running with Travis CI cause Travis CI complains console log is bigger than 4M.
> Recently we adopt log4j2 (STORM-833), but seems like we don't convert logback-test.xml to log4j2-test.xml so when Travis CI builds Storm, log is exceed 4M again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)