[
https://issues.apache.org/jira/browse/IGNITE-9726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644903#comment-16644903
]
Ryabov Dmitrii commented on IGNITE-9726:
----------------------------------------
They could appear in random commit and looks like they are fixed, because they
don't fail in the master. So, master refresh will remove them from
[blockers|https://mtcga.gridgain.com/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&baseBranchForTc=&branchForTc=pull%2F4859%2Fhead&action=Latest].
> 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)
