[jira] [Resolved] (IMPALA-6242) Flaky test: TimerCounterTest.CountersTestOneThread

["Tianyi Wang (JIRA)" <ji...@apache.org>]

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

Tianyi Wang resolved IMPALA-6242.
---------------------------------
    Resolution: Fixed

IMPALA-6242: Reduce flakiness in TimerCounterTest

The error threshold in TimerCounterTest is 15ms, which is still not
enough in some rare cases. This patch increases it to 30ms.

Change-Id: Ifc038908857060ccbabfe30c46e72fd93907f412
Reviewed-on: http://gerrit.cloudera.org:8080/8670
Reviewed-by: Tim Armstrong <ta...@cloudera.com>
Tested-by: Impala Public Jenkins


> Flaky test: TimerCounterTest.CountersTestOneThread
> --------------------------------------------------
>
>                 Key: IMPALA-6242
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6242
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.11.0
>            Reporter: Tianyi Wang
>            Assignee: Tianyi Wang
>            Priority: Critical
>              Labels: broken-build
>
> CountersTestOneThread failed in an release build. The difference between the time interval measured in spawned thread and that in main thread is more than expected.
> {noformat}
> be/src/util/runtime-profile-test.cc:673
> Expected: (stopwatch_value) >= (expected_value - TimerCounterTest::MAX_TIMER_ERROR_NS), actual: 250997548 vs 258086034
> {noformat}



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