[
https://issues.apache.org/jira/browse/KUDU-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757170#comment-17757170
]
ASF subversion and git services commented on KUDU-3432:
-------------------------------------------------------
Commit acd1622b0c77b40280753567130a815cbcd93081 in kudu's branch
refs/heads/master from kedeng
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=acd1622b0 ]
KUDU-3432: Fix flakiness in client-test.cc
The 'TestGetTableKeyRange' in 'client-test.cc' may
be unstable in certain cases. Through analysis, it
was determined that the split algorithm might encounter
some corner cases when handling written data.
To mitigate the impact of these cases on CI, I have
increased the amount of data written in the unit tests
and modified some logic in dance to enhance the robustness
of the unit tests.
Change-Id: I1e3fecc09f58d91fe9a8c6d20caa21938dd9c972
Reviewed-on: http://gerrit.cloudera.org:8080/20314
Reviewed-by: Alexey Serbin <[email protected]>
Tested-by: Alexey Serbin <[email protected]>
> TableKeyRangeTest.TestGetTableKeyRange is flaky
> -----------------------------------------------
>
> Key: KUDU-3432
> URL: https://issues.apache.org/jira/browse/KUDU-3432
> Project: Kudu
> Issue Type: Bug
> Components: client, test
> Affects Versions: 1.17.0
> Reporter: Alexey Serbin
> Priority: Major
> Attachments: client-test.4.00.txt.xz, client-test.4.txt.xz
>
>
> The {{TableKeyRangeTest.TestGetTableKeyRange}} scenario added with
> [cef110b31|https://github.com/apache/kudu/commit/cef110b314f94aadfd3274932e710d05b7cec97c]
> shows signs of flakiness. At least, I saw the following failure (DEBUG
> build configuration):
> {noformat}
> src/kudu/client/client-test.cc:8798: Failure
> Expected: (token_size_a) != (token_size_b), actual: 14 vs 14
> {noformat}
> I'm attaching the full log of the failed test scenario.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
