curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-139) Add slf4j logging implementation to test scope
Date Wed, 20 Aug 2014 01:42:18 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103215#comment-14103215
] 

ASF GitHub Bot commented on CURATOR-139:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/curator/pull/36


> Add slf4j logging implementation to test scope
> ----------------------------------------------
>
>                 Key: CURATOR-139
>                 URL: https://issues.apache.org/jira/browse/CURATOR-139
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Mike Drob
>
> When attempting to debug unit tests, it can be very difficult because the no-op logger
is used as the default slf4j implementation. We should add a test scoped log4j (or logback,
doesn't really matter) dependency so that test output is saved.
> Reasons against are that it potentially slows down the tests because of extra IO or that
it uses up a non-trivial amount of disk space. If either of these is the case, I feel that
they should be addressed separately. Logging can be specifically configured for the cases
where we have known issues.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message