[
https://issues.apache.org/jira/browse/IGNITE-11036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-11036:
--------------------------------------
Ignite Flags: (was: Docs Required)
> IgniteTcpCommunicationHandshakeWaitTest/IgniteTcpCommunicationHandshakeWaitSslTest
> fail in master
> --------------------------------------------------------------------------------------------------
>
> Key: IGNITE-11036
> URL: https://issues.apache.org/jira/browse/IGNITE-11036
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.8
> Reporter: Sergey Kosarev
> Assignee: Sergey Kosarev
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> On my local environment (Mac OS X) IgniteTcpCommunicationHandshakeWaitSslTest
> fails in 100% rate.
> {code}
> junit.framework.AssertionFailedError:
> Expected :3
> Actual :1
> <Click to see difference>
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at
> org.apache.ignite.spi.communication.tcp.IgniteTcpCommunicationHandshakeWaitTest.lambda$testHandshakeOnNodeJoining$0(IgniteTcpCommunicationHandshakeWaitTest.java:99)
> at
> org.apache.ignite.testframework.GridTestUtils.lambda$runAsync$2(GridTestUtils.java:1009)
> {code}
> I've investigated and found that the test overrides TcpDiscoverySpi but does
> not set ipFinder to the new object. Setting ipFinder solves the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
