ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amelchev Nikita (Jira)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-12386) The InvalidServerTest.testInvalidServer test is flacky
Date Thu, 21 Nov 2019 12:40:00 GMT
Amelchev Nikita created IGNITE-12386:
----------------------------------------

             Summary: The InvalidServerTest.testInvalidServer test is flacky
                 Key: IGNITE-12386
                 URL: https://issues.apache.org/jira/browse/IGNITE-12386
             Project: Ignite
          Issue Type: Test
            Reporter: Amelchev Nikita
            Assignee: Amelchev Nikita
             Fix For: 2.8


The InvalidServerTest.testInvalidServer test is flacky.

The reason is that in the test two clusters are started, instead of one. Because TcpDiscoveryMulticastIpFinder
is used by default.

{noformat}
03:41:32] Topology snapshot [ver=1, locNode=10ecdb9c, servers=1, clients=0, state=INACTIVE,
CPUs=5, offheap=19.0GB, heap=2.0GB]
[03:41:36] Topology snapshot [ver=1, locNode=20f59b4f, servers=1, clients=0, state=INACTIVE,
CPUs=5, offheap=19.0GB, heap=2.0GB]
[03:41:40] Topology snapshot [ver=2, locNode=cecf2df6, servers=2, clients=0, state=INACTIVE,
CPUs=5, offheap=19.0GB, heap=2.0GB]
{noformat}

[Fail example.|https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=4771562&_focus=233870]




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message