You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2015/05/07 20:36:00 UTC
[jira] [Commented] (ZOOKEEPER-2017) New tests for reconfig failure
cases
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533157#comment-14533157 ]
Chris Nauroth commented on ZOOKEEPER-2017:
------------------------------------------
The test suite {{ReconfigFailureCases}} that was introduced in this patch has not been running during pre-commit, because the build's test inclusion pattern looks for classes ending in "Test". I filed a patch on ZOOKEEPER-2182 to rename it to {{ReconfigFailureCasesTest}}.
> New tests for reconfig failure cases
> ------------------------------------
>
> Key: ZOOKEEPER-2017
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2017
> Project: ZooKeeper
> Issue Type: Test
> Components: tests
> Affects Versions: 3.5.0
> Reporter: Alexander Shraer
> Assignee: Alexander Shraer
> Priority: Minor
> Fix For: 3.5.1, 3.6.0
>
> Attachments: ZOOKEEPER-2017-v4.patch, ZOOKEEPER-2017-ver3.patch, ZOOKEEPER-2017.patch
>
>
> 1) New test file with some reconfig failure cases.
> 2) Moved testLeaderTimesoutOnNewQuorum from ReconfigTest to the new file
> 3) Added a check to standaloneDisabledTest.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)