[
https://issues.apache.org/jira/browse/KUDU-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854498#comment-17854498
]
ASF subversion and git services commented on KUDU-3584:
-------------------------------------------------------
Commit 5063e80e1ca26c5f1b763a6ce3e4708cd8196a26 in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=5063e80e1 ]
KUDU-3584 fix flakiness in TableKeyRangeTest
When running client-test in TSAN/ASAN builds, the
TableKeyRangeTest.TestGetTableKeyRange scenario would sometimes fail
on busy nodes. This patch addresses the issue by increasing the
timeout for scanners and for the write session, and making the related
code more robust overall.
I also took the liberty of cleaning up the related code.
Change-Id: I1efc2fe6ee7f2dfe94b52b14f1316ffbafd39d52
Reviewed-on: http://gerrit.cloudera.org:8080/21506
Reviewed-by: KeDeng <kdeng...@gmail.com>
Reviewed-by: Marton Greber <greber...@gmail.com>
Tested-by: Marton Greber <greber...@gmail.com>
> TableKeyRangeTest.TestGetTableKeyRange fails from time to time
> --------------------------------------------------------------
>
> Key: KUDU-3584
> URL: https://issues.apache.org/jira/browse/KUDU-3584
> Project: Kudu
> Issue Type: Sub-task
> Components: test
> Affects Versions: 1.17.0
> Reporter: Alexey Serbin
> Priority: Major
> Attachments: client-test.00.6.txt.xz, client-test.01.6.txt.xz
>
>
> The {{TableKeyRangeTest.TestGetTableKeyRange}} scenario in {{client-test}} is
> flaky, especially in sanitizer builds, failing from time to time with error
> like below:
> {noformat}
> src/kudu/client/client-test.cc:9050: Failure
> Expected equality of these values:
> 1000
> CountRows(tokens)
> Which is: 990
> {noformat}
> Logs from two different failed runs are attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
