You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (Jira)" <ji...@apache.org> on 2023/08/22 01:46:00 UTC

[jira] [Resolved] (KUDU-3432) TableKeyRangeTest.TestGetTableKeyRange is flaky

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

Alexey Serbin resolved KUDU-3432.
---------------------------------
    Fix Version/s: 1.18.0
       Resolution: Fixed

> 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
>             Fix For: 1.18.0
>
>         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)