[
https://issues.apache.org/jira/browse/CASSANDRA-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940383#comment-14940383
]
Jim Witschey commented on CASSANDRA-10289:
------------------------------------------
The diff I posted applies cleanly to the cassandra-2.2 and cassandra-3.0
branches. cassandra-3.0 fails with the same errors as on trunk, and
cassandra-2.2 fails with a couple more because of bug fixes and features that
only exist in 3.0+.
However, the changes don't apply cleanly to 2.1. I've filed another ticket
(CASSANDRA-10432) to track fixing them on all supported versions. For the
moment, I propose applying the changes as-is to 2.2+ or 3.0+. I don't think
it's worth blocking merge on fixing the tests all the way back.
> Fix cqlshlib tests
> ------------------
>
> Key: CASSANDRA-10289
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10289
> Project: Cassandra
> Issue Type: Bug
> Components: Tests
> Reporter: Jim Witschey
> Assignee: Jim Witschey
> Labels: cqlsh
> Fix For: 3.0.0 rc2
>
> Attachments: trunk-10289.diff
>
>
> The cqlsh tests in trunk haven't been running for a while:
> http://cassci.datastax.com/view/All_Jobs/job/trunk_cqlshlib/423/testReport/
> This looks like the driver errors that happened because of CASSANDRA-6717.
> Not sure why it's happening now; the driver installation looks normal to me
> on those jobs. [~mshuler]?
> There were also some changes to cqlsh itself that also broke the test
> harness, but I believe those are fixed here:
> https://github.com/mambocab/cassandra/tree/fix-cqlsh-tests
> Once the tests are running successfully on CassCI, I'll test my patch and
> mark as patch available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
