[
https://issues.apache.org/jira/browse/METRON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644960#comment-15644960
]
ASF GitHub Bot commented on METRON-541:
---------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/347
Resolved a merge conflict with SnortParserTest and changed Travis
configuration to not run mvn install (since we're already doing it as part of
our tests). Check out those logs! The stack traces should be gone after #344.
> Set log levels for Metron components
> ------------------------------------
>
> Key: METRON-541
> URL: https://issues.apache.org/jira/browse/METRON-541
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
> Priority: Critical
>
> When running unit or integration tests the log output is very verbose. This
> makes it difficult to determine what the problem is when something goes wrong
> and also intermittently causes Travis to hit it's output threshold and fail.
> The log levels should be consistent across all components and there should be
> logging profiles available for different scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
