You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2020/06/26 12:22:00 UTC

[jira] [Updated] (IGNITE-12641) IgniteSequenceInternalCleanupTest flacky after IGNITE-12598

     [ https://issues.apache.org/jira/browse/IGNITE-12641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Plekhanov updated IGNITE-12641:
---------------------------------------
    Fix Version/s: 2.9

> IgniteSequenceInternalCleanupTest flacky after IGNITE-12598
> -----------------------------------------------------------
>
>                 Key: IGNITE-12641
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12641
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Nikolay Izhikov
>            Assignee: Nikolay Izhikov
>            Priority: Major
>              Labels: IEP-35
>             Fix For: 2.9
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> IgniteSequenceInternalCleanupTest#deactivate is flacky after IGNITE-12598
> The test expects that cache metrics will be reset after cluster deactivation and subsequent cache stop.
> But this was changed intentionally in IGNITE-12598.
> Test not always fail because it asserts cluster metrics value which updated concurrently with the test thread. 
> We should fix the assert.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)