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

[jira] [Resolved] (IGNITE-8061) GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity

     [ https://issues.apache.org/jira/browse/IGNITE-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vyacheslav Koptilin resolved IGNITE-8061.
-----------------------------------------
    Resolution: Cannot Reproduce

Looks like the test is stable on the master branch
https://ci.ignite.apache.org/test/-6279625182504164903?currentProjectId=IgniteTests24Java8&branch=%3Cdefault%3E

I would close the ticket. Please reopen this if you think that it still needs to be analyzed.

> GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-8061
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8061
>             Project: Ignite
>          Issue Type: Bug
>          Components: data structures
>    Affects Versions: 2.4
>            Reporter: Andrey Kuznetsov
>            Priority: Major
>         Attachments: log.txt
>
>
> The log attached contains 'Test has been timed out and will be interrupted' message, but does not contain subsequent 'Test has been timed out [test=...'.
> Known facts:
> * There is pending GridDhtColocatedLockFuture in the log.
> * On timeout, InterruptedException comes to doTestCountDownLatch, but finally-block contains the code leading to distributed locking.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)