This is my fault, introduced within https://issues.apache.org/jira/browse/IGNITE-10715
I have no idea why it had not been failed during testing on TC. I will prepare the fix quickly. On Tue, Dec 25, 2018 at 2:37 AM <dpavlov.ta...@gmail.com> wrote: > > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. You are more than > welcomed to help. > > If your changes can lead to this failure(s): We're grateful that you were a > volunteer to make the contribution to this project, but things change and you > may no longer be able to finalize your contribution. > Could you respond to this email and indicate if you wish to continue and fix > test failures or step down and some committer may revert you commit. > > * New stable failure of a flaky test in master > IgniteClientConnectTest.testClientConnectToBigTopology > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=9021926721143358489&branch=%3Cdefault%3E&tab=testDetails > Changes may lead to failure were done by > - ilya.kasnacheev > https://ci.ignite.apache.org/viewModification.html?modId=850683 > - daradurvs > https://ci.ignite.apache.org/viewModification.html?modId=850663 > - antonovsergey93 > https://ci.ignite.apache.org/viewModification.html?modId=850675 > > - Here's a reminder of what contributors were agreed to do > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > - Should you have any questions please contact dev@ignite.apache.org > > Best Regards, > Apache Ignite TeamCity Bot > https://github.com/apache/ignite-teamcity-bot > Notification generated at 02:36:58 25-12-2018 -- Best Regards, Vyacheslav D.
