[
https://issues.apache.org/jira/browse/IGNITE-8036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411683#comment-16411683
]
Sergey Chugunov commented on IGNITE-8036:
-----------------------------------------
Artifacts: [PR|https://github.com/apache/ignite/pull/3693], [TC
run|https://ci.ignite.apache.org/viewQueued.html?itemId=1154905&tab=queuedBuildOverviewTab].
Decided to not create upsource review for this tiny change. Also TC Run is only
for Ignite Queries [2] suite; it is the only one affected.
> DynamicColumnsAbstractConcurrentSelfTest should not use MulticastIpFinder
> -------------------------------------------------------------------------
>
> Key: IGNITE-8036
> URL: https://issues.apache.org/jira/browse/IGNITE-8036
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
>
> It turned out that DynamicColumnsAbstractConcurrentSelfTest prepares
> IgniteConfiguration without redefining default MulticastIpFinder which causes
> flaky fails of tests later.
>
> VmIpFinder should be used instead of MulticastIpFinder.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
