[jira] [Comment Edited] (IGNITE-9726) GridCacheAbstractFailoverSelfTest may lock all suite on put/remove cache operations

["Ryabov Dmitrii (JIRA)" <ji...@apache.org>]

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

Ryabov Dmitrii edited comment on IGNITE-9726 at 10/4/18 2:54 PM:
-----------------------------------------------------------------

Hi, Alexey,

If this test can hangs rarely then we need to do mass run for this test. Please, create separate PR with suite filled with at least 100 instances of this test and run it on TeamCity.


was (Author: somefire):
Hi, Alexey,

If this method can hangs then we need to do mass run for this test. Please, create separate PR with suite filled with at least 100 instances of this test and run it on TeamCity.

> GridCacheAbstractFailoverSelfTest may lock all suite on put/remove cache operations
> -----------------------------------------------------------------------------------
>
>                 Key: IGNITE-9726
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9726
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Platonov
>            Assignee: Alexey Platonov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.7
>
>
> Example of timeouts:
> [https://ci.ignite.apache.org/viewLog.html?buildId=1944646&buildTypeId=IgniteTests24Java8_CacheFailover2&tab=buildLog]
> method testConstantTopologyChange can misses interrupt from test runner and lock suite
> see that after thread dump put/remove cache operations will continue in test
> testOptimisticSerializableTxConstantTopologyChange



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