ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9531) ZookeeperDiscovery testClientReconnect is flaky in master
Date Tue, 11 Sep 2018 10:57:00 GMT

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

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

GitHub user avplatonov opened a pull request:

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

    IGNITE-9531: ZookeeperDiscovery testClientReconnect is flaky in master

    

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

    $ git pull https://github.com/gridgain/apache-ignite ignite-9531

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

    https://github.com/apache/ignite/pull/4722.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 #4722
    
----
commit f6ab10a1a78f4c17ba133acdbae76516b5c0d0ac
Author: Alexey Platonov <aplatonovv@...>
Date:   2018-09-11T10:55:27Z

    add test assertions

commit 5d79313bd92d66c562365d8287536b011c0597cc
Author: Alexey Platonov <aplatonovv@...>
Date:   2018-09-11T10:55:44Z

    Merge branch 'master' of https://github.com/apache/ignite into ignite-9531

----


> ZookeeperDiscovery testClientReconnect is flaky in master
> ---------------------------------------------------------
>
>                 Key: IGNITE-9531
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9531
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Platonov
>            Assignee: Alexey Platonov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.8
>
>
> The test IgniteClientReconnectCacheTest#testReconnect periodically.
> From the logs I see that the hang is caused by assertion error:
> {code}
> junit.framework.AssertionFailedError: expected:<22> but was:<null>
>     at junit.framework.Assert.fail(Assert.java:57)
>     at junit.framework.Assert.failNotEquals(Assert.java:329)
>     at junit.framework.Assert.assertEquals(Assert.java:78)
>     at junit.framework.Assert.assertEquals(Assert.java:86)
>     at junit.framework.TestCase.assertEquals(TestCase.java:253)
>     at org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnect(IgniteClientReconnectCacheTest.java:321)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
>     at junit.framework.TestCase.runTest(TestCase.java:176)
>     at org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2177)
>     at org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:143)
>     at org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2092)
>     at java.lang.Thread.run(Thread.java:748)
> {code}



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

Mime
View raw message