ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8061) GridCachePartitionedDataStructuresFailoverSelfTest.testCountDownLatchConstantMultipleTopologyChange may hang on TeamCity
Date Thu, 27 Sep 2018 10:28:00 GMT

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

Vladimir Ozerov commented on IGNITE-8061:
-----------------------------------------

Moved to 2.8 due to inactivity. Please feel free to move back if you will be able to complete
the ticket by AI 2.7 code freeze date, September 30, 2018.

> 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
>             Fix For: 2.7
>
>         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
(v7.6.3#76005)

Mime
View raw message