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-9726) GridCacheAbstractFailoverSelfTest may lock all suite on put/remove cache operations
Date Wed, 10 Oct 2018 11:34:00 GMT

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

Vladimir Ozerov commented on IGNITE-9726:
-----------------------------------------

[~SomeFire], [~aplatonov], Igniters,
Any news on the ticket? Today is the last day when we are ready to keep non-blocker tickets
on AI 2.7. Otherwise stability of AI 2.7 might be compromised. Please make sure to either
merge the ticket today, or move it to the next version.

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

Mime
View raw message