[
https://issues.apache.org/jira/browse/KUDU-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876423#comment-17876423
]
ASF subversion and git services commented on KUDU-3611:
-------------------------------------------------------
Commit d2a9636e30b41593ccf056bbae9d47e10aa3b193 in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=d2a9636e3 ]
KUDU-3611: fix flakiness in one scenario of rpc-test
This patch addresses a rare flakiness in the
TestRpc.TimedOutOnResponseMetricServiceQueue scenario.
Change-Id: I080e5ea5beaa74e0220bc6ae14d2f926d5602f0f
Reviewed-on: http://gerrit.cloudera.org:8080/21710
Tested-by: Kudu Jenkins
Reviewed-by: Marton Greber <greber...@gmail.com>
> Rare flakiness in TestRpc.TimedOutOnResponseMetricServiceQueue
> --------------------------------------------------------------
>
> Key: KUDU-3611
> URL: https://issues.apache.org/jira/browse/KUDU-3611
> Project: Kudu
> Issue Type: Bug
> Components: test
> Reporter: Alexey Serbin
> Priority: Minor
> Attachments: rpc-test.4.txt.xz
>
>
> The TimedOutOnResponseMetricServiceQueue scenario of TestRpc fails in very
> rare cases with error message like below:
> {noformat}
> src/kudu/rpc/rpc-test.cc:1427: Failure
> Expected equality of these values:
> 3
> latency_histogram->TotalCount()
> Which is: 2
> {noformat}
> Full log is attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
