You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2019/10/23 15:46:00 UTC
[jira] [Commented] (IGNITE-12323) Test GridCommandHandlerTest.
testBaselineAutoAdjustmentAutoRemoveNode is flaky
[ https://issues.apache.org/jira/browse/IGNITE-12323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957980#comment-16957980 ]
Ignite TC Bot commented on IGNITE-12323:
----------------------------------------
{panel:title=Branch: [pull/7001/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=4720381&buildTypeId=IgniteTests24Java8_RunAll]
> Test GridCommandHandlerTest. testBaselineAutoAdjustmentAutoRemoveNode is flaky
> ------------------------------------------------------------------------------
>
> Key: IGNITE-12323
> URL: https://issues.apache.org/jira/browse/IGNITE-12323
> Project: Ignite
> Issue Type: Test
> Reporter: Amelchev Nikita
> Assignee: Amelchev Nikita
> Priority: Minor
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Test {{GridCommandHandlerTest. testBaselineAutoAdjustmentAutoRemoveNode}} is flaky.
> The reason is that node stopping may be more than the auto adjust timeout. This cause assertion error on topology size check:
> {code:java}
> assertEquals(EXIT_CODE_OK, execute("--baseline", "auto_adjust", "enable", "timeout", "2000"));
> assertEquals(3, ignite.cluster().currentBaselineTopology().size());
> stopGrid(2); // May be more than 2 seconds
> assertEquals(3, ignite.cluster().currentBaselineTopology().size()); // Fails.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)