You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Platonov (JIRA)" <ji...@apache.org> on 2018/10/10 11:55:00 UTC

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

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

Alexey Platonov updated IGNITE-9726:
------------------------------------
    Fix Version/s:     (was: 2.7)
                   2.8

> 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.8
>
>
> 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)