[
https://issues.apache.org/jira/browse/ZOOKEEPER-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332305#comment-15332305
]
Hudson commented on ZOOKEEPER-2137:
-----------------------------------
SUCCESS: Integrated in ZooKeeper-trunk #2961 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2961/])
ZOOKEEPER-2137: Make testPortChange() less flaky (Michael Han via phunt)
(phunt:
[http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1748608])
* trunk/CHANGES.txt
* trunk/src/java/test/org/apache/zookeeper/test/ReconfigTest.java
> Make testPortChange() less flaky
> --------------------------------
>
> Key: ZOOKEEPER-2137
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2137
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: tests
> Affects Versions: 3.5.0
> Reporter: Hongchao Deng
> Assignee: Michael Han
> Labels: flakey
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2137-cb.patch, ZOOKEEPER-2137.patch,
> ZOOKEEPER-2137.patch, ZOOKEEPER-2137.patch, ZOOKEEPER-2137.patch
>
>
> The cause of flaky failure of testPortChange() is a race in sync().
> I figured out it could take some time to fix sync(). Meanwhile, we can make
> testPortChange() less flaky by doing reconfig on the leader. We can change
> this back in the fix of ZOOKEEPER-2136.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
