Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Fri, 8 Nov 2013 06:55:23 +0000 (UTC)
From: "Patrick Hunt (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.12676962.1383256032773.40912.1383893723400@arcas>
In-Reply-To: <JIRA.12676962.1383256032773@arcas>
References: <JIRA.12676962.1383256032773@arcas>
Subject: [jira] [Commented] (ZOOKEEPER-1806)
 testCurrentServersAreObserversInNextConfig failing frequently on trunk with
 non-jdk6
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Patrick Hunt commented on ZOOKEEPER-1806:
-----------------------------------------

I'm not sure, is that really the issue? What does junit mean when it says "crashed"? Did the jvm itself crash?

> 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)