[
https://issues.apache.org/jira/browse/IGNITE-9858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648061#comment-16648061
]
ASF GitHub Bot commented on IGNITE-9858:
----------------------------------------
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/4977
IGNITE-9858
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-9858
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4977.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4977
----
commit dab8e7afc309cdccfd717bf57f46d174e9d9d82a
Author: pereslegin-pa <xxtern@...>
Date: 2018-10-12T15:50:41Z
IGNITE-9858 Test fix.
----
> [Test Failed] SystemCacheNotConfiguredTest#test flaky fails on TC (timeout).
> ----------------------------------------------------------------------------
>
> Key: IGNITE-9858
> URL: https://issues.apache.org/jira/browse/IGNITE-9858
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Pavel Pereslegin
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> SystemCacheNotConfiguredTest hangs sometimes on TeamCity (timeout).
> Example of such failures on master branch:
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&buildTypeId=&tab=testDetails&testNameId=-2762467041583095183&order=TEST_STATUS_DESC&itemsCount=50&branch_IgniteTests24Java8=%3Cdefault%3E]
> Typically client node cannot join server, when client discovery SPI
> initializes before server discovery, because client ipfinder don't registers
> local node addresses (see
> TcpDiscoveryIpFinderAdapter#initializeLocalAddresses).
> {noformat}
> [2018-10-11 18:03:49,794][WARN
> ][tcp-client-disco-msg-worker-#57%client%][TcpDiscoverySpi] IP finder
> returned empty addresses list. Please check IP finder configuration. Will
> retry every 2000 ms. Change 'reconnectDelay' to configure the frequency of
> retries.{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
