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 2013/10/31 22:49:19 UTC

[jira] [Assigned] (ZOOKEEPER-1806) testCurrentServersAreObserversInNextConfig failing frequently on trunk with non-jdk6

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

Patrick Hunt reassigned ZOOKEEPER-1806:
---------------------------------------

    Assignee: Alexander Shraer

Alex can you take a look? This test was introduced in ZOOKEEPER-107 " Allow dynamic changes to server cluster membership (Alex Shraer via breed)"

> testCurrentServersAreObserversInNextConfig failing frequently on trunk with non-jdk6
> ------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1806
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1806
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.5.0
>            Reporter: Patrick Hunt
>            Assignee: Alexander Shraer
>             Fix For: 3.5.0
>
>
> testCurrentServersAreObserversInNextConfig failing frequently on trunk with jdk7
> I see a number of failures recently on this test. Is it a real issue or flakey? Perhaps due to re-ordering/cleanup with jdk7 as we've seen with some other tests? (I don't see this test failing with jdk6)



--
This message was sent by Atlassian JIRA
(v6.1#6144)