[ https://issues.apache.org/jira/browse/IGNITE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504572#comment-16504572 ]
Amelchev Nikita commented on IGNITE-6010: ----------------------------------------- The test became flaky after commit e05c012 where the timeout was decreased to 20s. Sometimes curators closed on session timeout (60 sec) and fail the test. I prepared PR to fix the test: - I added the additional block to ensure that clients were connected. - Now session closes expected without timeouts and "wait for condition" block is excess. > ZookeeperIpFinderTest.testFourNodesKillRestartZookeeper fails sometimes > ----------------------------------------------------------------------- > > Key: IGNITE-6010 > URL: https://issues.apache.org/jira/browse/IGNITE-6010 > Project: Ignite > Issue Type: Bug > Components: zookeeper > Affects Versions: 2.1 > Reporter: Ilya Lantukh > Assignee: Amelchev Nikita > Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > {noformat} > junit.framework.AssertionFailedError: null > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertTrue(Assert.java:31) > at junit.framework.TestCase.assertTrue(TestCase.java:201) > at > org.apache.ignite.spi.discovery.tcp.ipfinder.zk.ZookeeperIpFinderTest.testFourNodesKillRestartZookeeper(ZookeeperIpFinderTest.java:365) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)