[ 
https://issues.apache.org/jira/browse/IGNITE-10579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711568#comment-16711568
 ] 

ASF GitHub Bot commented on IGNITE-10579:
-----------------------------------------

GitHub user NSAmelchev opened a pull request:

    https://github.com/apache/ignite/pull/5591

    IGNITE-10579 IgniteCacheContinuousQueryReconnectTest.testReconnectServer is 
flaky in master.

    PR for TC mass runs

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/NSAmelchev/ignite ignite-10579

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/5591.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 #5591
    
----
commit e6be7501a5e9582c8de533ed0cd9e14e438b51fa
Author: NSAmelchev <nsamelchev@...>
Date:   2018-12-06T15:03:53Z

    Test mass runs

----


> IgniteCacheContinuousQueryReconnectTest.testReconnectServer is flaky in 
> master.
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-10579
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10579
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Amelchev Nikita
>            Assignee: Amelchev Nikita
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>
> Next tests are flaky in master: 
> IgniteCacheContinuousQueryReconnectTest.testReconnectServer
> IgniteCacheContinuousQueryReconnectTest.testReconnectClient
> Test exception: 
> {noformat}
> junit.framework.AssertionFailedError: expected:<2> but was:<1>
>     at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryReconnectTest.putAndCheck(IgniteCacheContinuousQueryReconnectTest.java:111)
>     at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryReconnectTest.testReconnect(IgniteCacheContinuousQueryReconnectTest.java:179)
>     at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryReconnectTest.testReconnectServer(IgniteCacheContinuousQueryReconnectTest.java:93)
> {noformat}
> [Test 
> history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-4837559557126450615&branch=%3Cdefault%3E&tab=testDetails]
> By logs I found that possible reason is that started node doesn't see 
> cluster: 
> {noformat}
> startGrid(0);
>       Topology snapshot [ver=1, locNode=0b292f90, servers=1, clients=0
> startGrid(1); //client
>       Topology snapshot [ver=2, locNode=0b292f90, servers=1, clients=1
>       Topology snapshot [ver=2, locNode=693848f6, servers=1, clients=1
> startGrid(2);
>       Topology snapshot [ver=3, locNode=0b292f90, servers=2, clients=1
>       Topology snapshot [ver=3, locNode=693848f6, servers=2, clients=1
>       Topology snapshot [ver=3, locNode=99a406a5, servers=2, clients=1
> stopGrid(0);
>       Topology snapshot [ver=4, locNode=99a406a5, servers=1, clients=1
>       Topology snapshot [ver=4, locNode=693848f6, servers=1, clients=1
> startGrid(3);
>       Topology snapshot [ver=1, locNode=8d9ef192, servers=1, clients=0
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to