[
https://issues.apache.org/jira/browse/IGNITE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737922#comment-16737922
]
Sergey Chugunov commented on IGNITE-10809:
------------------------------------------
[~DmitriyGovorukhin] it is the final fix: I refactored
persistence/non-persistence tests trying to change code as little as possible.
To me test logic makes sense in both cases so I kept both scenarios. But if you
have a better idea of how this could be refactored, lets try it.
> IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3
> fails in master
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-10809
> URL: https://issues.apache.org/jira/browse/IGNITE-10809
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Test logic involves independent activation two sets of nodes and then their
> join into a single cluster.
> After introducing BaselineTopology concept in 2.4 version this action became
> prohibited to enforce data integrity.
> Test should be refactored to take this into account.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
