[
https://issues.apache.org/jira/browse/IGNITE-29204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132182#comment-18132182
]
Ignite TC Bot commented on IGNITE-29204:
----------------------------------------
{panel:title=Branch: [pull/13747/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13747/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9441261&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9441261
rerunBuildIds=none{color}
> Fix string-based version comparison in IndexTypesCompatibilityTest
> ------------------------------------------------------------------
>
> Key: IGNITE-29204
> URL: https://issues.apache.org/jira/browse/IGNITE-29204
> Project: Ignite
> Issue Type: Bug
> Reporter: Dmitry Werner
> Assignee: Dmitry Werner
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IndexTypesCompatibilityTest#validateResultingCacheData compares Ignite
> versions as strings:
> igniteVer.compareTo("2.8.0") < 0 // Binary
> igniteVer.compareTo("2.7.0") < 0 // UUID
> Lexicographically "2.10.0".."2.18.0" < "2.8.0", so Binary and UUID index
> checks are silently skipped for all versions since 2.10.0 (on JDK 17+ the
> checks never run at all).
> Fix: compare IgniteReleasedVersion values instead of strings.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
