[jira] [Commented] (IGNITE-8036) DynamicColumnsAbstractConcurrentSelfTest should not use MulticastIpFinder
[ https://issues.apache.org/jira/browse/IGNITE-8036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413871#comment-16413871 ] ASF GitHub Bot commented on IGNITE-8036: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3693 > 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)
[jira] [Commented] (IGNITE-8036) DynamicColumnsAbstractConcurrentSelfTest should not use MulticastIpFinder
[ 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)
[jira] [Commented] (IGNITE-8036) DynamicColumnsAbstractConcurrentSelfTest should not use MulticastIpFinder
[ https://issues.apache.org/jira/browse/IGNITE-8036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411675#comment-16411675 ] ASF GitHub Bot commented on IGNITE-8036: GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/3693 IGNITE-8036 MulticastIpFinder is replaced with VmIpFinder You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8036 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3693.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 #3693 commit 870d7256c64c20b8c09c263f8f83bd5ec179d7a3 Author: Sergey Chugunov Date: 2018-03-23T16:22:05Z IGNITE-8036 MulticastIpFinder is replaced with VmIpFinder > 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)
