You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Chia-Ping Tsai (JIRA)" <ji...@apache.org> on 2018/01/05 08:32:00 UTC

[jira] [Resolved] (HBASE-16936) TestRateLimiter#testOverconsumptionFixedIntervalRefillStrategy is flaky

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

Chia-Ping Tsai resolved HBASE-16936.
------------------------------------
    Resolution: Duplicate

HBASE-19490

> TestRateLimiter#testOverconsumptionFixedIntervalRefillStrategy is flaky
> -----------------------------------------------------------------------
>
>                 Key: HBASE-16936
>                 URL: https://issues.apache.org/jira/browse/HBASE-16936
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>            Reporter: Dima Spivak
>            Assignee: huaxiang sun
>
> Seeing this once every month or two in-house. Looks like it's a timing-based test, which makes it prone to flakiness, but I've noticed that whenever it fails, it fails with the same {{AssertionError}} (including values), so it'd be worth digging into. In our case:
> {noformat}
> expected:<1000> but was:<999>
> Stack Trace:
> java.lang.AssertionError: expected:<1000> but was:<999>
>         at org.apache.hadoop.hbase.quotas.TestRateLimiter.testOverconsumptionFixedIntervalRefillStrategy(TestRateLimiter.java:119)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)