[ https://issues.apache.org/jira/browse/IGNITE-9726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646651#comment-16646651 ]
Alexey Goncharuk commented on IGNITE-9726: ------------------------------------------ This is indeed a flaky test not related to the change, now looks good. > 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)