You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Rei Odaira (JIRA)" <ji...@apache.org> on 2016/06/02 23:23:59 UTC
[jira] [Updated] (CASSANDRA-11948) Wrong ByteBuffer comparisons in
TimeTypeTest
[ https://issues.apache.org/jira/browse/CASSANDRA-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rei Odaira updated CASSANDRA-11948:
-----------------------------------
Flags: Patch
Attachment: 11948-2.2.txt
Description: The last three tests in org.apache.cassandra.db.marshal.TimeTypeTest compare the returned values of AbstractType.compare() with -1 or 1. However, AbstractType.compare() is supposed to return a negative integer, zero, or a positive integer, and it does not necessarily return -1 or 1. (was: The last three tests in org.apache.cassandra.db.marshal.TimeTypeTest compare the returned values of AbstractType.compare() with -1 or 1. However, AbstractType.compare() is supposed to return a negative integer, zero, or a positive integer, and it does not necessarily return -1 or 1. I will submit a patch shortly.)
> Wrong ByteBuffer comparisons in TimeTypeTest
> --------------------------------------------
>
> Key: CASSANDRA-11948
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11948
> Project: Cassandra
> Issue Type: Bug
> Components: Testing
> Reporter: Rei Odaira
> Priority: Minor
> Fix For: 2.2.x, 3.0.x, 3.x
>
> Attachments: 11948-2.2.txt
>
>
> The last three tests in org.apache.cassandra.db.marshal.TimeTypeTest compare the returned values of AbstractType.compare() with -1 or 1. However, AbstractType.compare() is supposed to return a negative integer, zero, or a positive integer, and it does not necessarily return -1 or 1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)