You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksandr Polovtcev (Jira)" <ji...@apache.org> on 2023/10/19 06:55:00 UTC

[jira] [Commented] (IGNITE-20545) Test IgniteRpcTest.testDisconnect is flaky on TC

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

Aleksandr Polovtcev commented on IGNITE-20545:
----------------------------------------------

I wasn't able to reproduce this problem locally, I think it may be related to some stale Ignite instances running on TC. I'm going to add some logging and check the TC during the next failure

> Test IgniteRpcTest.testDisconnect is flaky on TC
> ------------------------------------------------
>
>                 Key: IGNITE-20545
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20545
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Sergey Chugunov
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>
> Test failed recently on main branch ([failed run|https://ci.ignite.apache.org/viewLog.html?buildId=7536503&buildTypeId=ApacheIgnite3xGradle_Test_RunAllTests]), there is an assertion in test logs:
> {code:java}
> org.opentest4j.AssertionFailedError: expected: <true> but was: <false>
> at app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at app//org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
> at app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
> at app//org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:31)
> at app//org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:180)
> at app//org.apache.ignite.raft.jraft.rpc.AbstractRpcTest.testDisconnect(AbstractRpcTest.java:128){code}
> Test history shows that it fails occasionally in different branches with the same error in logs.
> Looks like there is some kind of race between events in test logic.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)