[
https://issues.apache.org/jira/browse/IGNITE-10809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737968#comment-16737968
]
Dmitriy Govorukhin commented on IGNITE-10809:
---------------------------------------------
[~sergey-chugunov] I suggest the use GridTestUtils.assertThrows in case if we
really wait for an exception in the test.
{code}
for (int i = 0; i < 4; i++) {
if (!persistenceEnabled()) {
startGrid(i);
}
else {
GridTestUtils.assertThrows(log, new Callable<Object>() {
@Override public Object call() throws Exception {
startGrid(i);
return null;
}
}, Exception.class, EXPECTED_MSG);
}
}
{code}
> 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)
