You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2009/07/31 06:26:14 UTC
[jira] Created: (ZOOKEEPER-492) the tests should have their own
log4j.properties
the tests should have their own log4j.properties
------------------------------------------------
Key: ZOOKEEPER-492
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-492
Project: Zookeeper
Issue Type: Bug
Components: tests
Affects Versions: 3.2.0, 3.1.1
Reporter: Patrick Hunt
Priority: Minor
Fix For: 3.3.0
the tests currently rely (QuorumPeerMainTest in particular) on conf/log4j.properties. if the user changes this file
and then runs the tests the tests may fail. the tests should have their own log4j.properties maintained w/in the test
directory itself, separate from conf/log4j.properties
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-492) the tests should have their own
log4j.properties
Posted by "Abmar Barros (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898802#action_12898802 ]
Abmar Barros commented on ZOOKEEPER-492:
----------------------------------------
I have just checked out the ZooKeeper trunk in Eclipse (running on Windows) and 3/5 tests from the QuorumPeerMainTest fail due to a NullPointerException while recovering CONSOLE appender. Is this supposed to happen?
> the tests should have their own log4j.properties
> ------------------------------------------------
>
> Key: ZOOKEEPER-492
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-492
> Project: Zookeeper
> Issue Type: Bug
> Components: tests
> Affects Versions: 3.1.1, 3.2.0
> Reporter: Patrick Hunt
> Priority: Minor
> Fix For: 3.4.0
>
>
> the tests currently rely (QuorumPeerMainTest in particular) on conf/log4j.properties. if the user changes this file
> and then runs the tests the tests may fail. the tests should have their own log4j.properties maintained w/in the test
> directory itself, separate from conf/log4j.properties
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-492) the tests should have their own
log4j.properties
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898975#action_12898975 ]
Patrick Hunt commented on ZOOKEEPER-492:
----------------------------------------
It happens today because we rely on a particular setup of log4j, in eclipse if you don't add the conf directory to the "run as junit test" classpath it won't pick up that log4j.properties and as a result the test will fail. try that. We should have a test specific log4j.properties (hence this jira).
> the tests should have their own log4j.properties
> ------------------------------------------------
>
> Key: ZOOKEEPER-492
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-492
> Project: Zookeeper
> Issue Type: Bug
> Components: tests
> Affects Versions: 3.1.1, 3.2.0
> Reporter: Patrick Hunt
> Priority: Minor
> Fix For: 3.4.0
>
>
> the tests currently rely (QuorumPeerMainTest in particular) on conf/log4j.properties. if the user changes this file
> and then runs the tests the tests may fail. the tests should have their own log4j.properties maintained w/in the test
> directory itself, separate from conf/log4j.properties
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.