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

Posted to issues@ignite.apache.org by "Amelchev Nikita (Jira)" <ji...@apache.org> on 2022/05/26 07:25:00 UTC

[jira] [Commented] (IGNITE-17035) The testChangeSnapshotTransferRateInRuntime test is flaky.

    [ https://issues.apache.org/jira/browse/IGNITE-17035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542383#comment-17542383 ] 

Amelchev Nikita commented on IGNITE-17035:
------------------------------------------

Multiple tests run: https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtilityZookeeper/6453509?showRootCauses=false

> The testChangeSnapshotTransferRateInRuntime test is flaky.
> ----------------------------------------------------------
>
>                 Key: IGNITE-17035
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17035
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Amelchev Nikita
>            Assignee: Amelchev Nikita
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The test is flaky: 
> https://ci2.ignite.apache.org/test/5720057658324237232?currentProjectId=IgniteTests24Java8&branch=%3Cdefault%3E&expandTestHistoryChartSection=true
> The reason - it does not take into account release time of BasicRateLimiter#acquire() after rate set to unlimited.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)