[
https://issues.apache.org/jira/browse/IGNITE-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16548076#comment-16548076
]
Pavel Kovalenko commented on IGNITE-8783:
-----------------------------------------
[~avinogradov] Ok, now it makes sense. Btw, I propose to add explicit test with
the hanging scenario to make sure that after some future changes everything
will work well. 18% of flaky in suites not related directly to this
functionality is not good point to demonstrate the fix of the problem. So,
after adding test, I think PR will be ready to merge.
We can make call on Friday when I return from vacation completely :)
> Failover tests periodically cause hanging of the whole Data Structures suite
> on TC
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-8783
> URL: https://issues.apache.org/jira/browse/IGNITE-8783
> Project: Ignite
> Issue Type: Bug
> Components: data structures
> Reporter: Ivan Rakov
> Assignee: Anton Vinogradov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> History of suite runs:
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures&tab=buildTypeHistoryList&branch_IgniteTests24Java8=%3Cdefault%3E
> Chance of suite hang is 18% in master (based on previous 50 runs).
> Hang is always caused by one of the following failover tests:
> {noformat}
> GridCacheReplicatedDataStructuresFailoverSelfTest#testAtomicSequenceConstantTopologyChange
> GridCachePartitionedDataStructuresFailoverSelfTest#testFairReentrantLockConstantTopologyChangeNonFailoverSafe
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
