[
https://issues.apache.org/jira/browse/IGNITE-28880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095364#comment-18095364
]
Vladislav Pyatkov commented on IGNITE-28880:
--------------------------------------------
This is an obvious fix, and I'm sure there is no other proof except the green
flag in the PR.
> IndexQueryInlineSizesTest.testFixedInlineKeys is flaky
> ------------------------------------------------------
>
> Key: IGNITE-28880
> URL: https://issues.apache.org/jira/browse/IGNITE-28880
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-2, teamcity
> Time Spent: 20m
> Remaining Estimate: 0h
>
> IndexQueryInlineSizesTest.check() generates range bounds as:
> {code}
> int low = r.nextInt(CNT / 2);
> int high = low + r.nextInt(CNT / 2);
> {code}
> When the second nextInt() returns 0, high == low. The index query then
> correctly returns no rows for conditions fld1 > low and fld2 < high, but the
> test asserts high - low - 1, which equals -1.
> This produces a flaky failure such as:
> {noformat}
> IndexQueryInlineSizesTest.testFixedInlineKeys[inlineSize=8]
> java.lang.AssertionError: expected:<-1> but was:<0>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
