[
https://issues.apache.org/jira/browse/CASSANDRA-10896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Witschey resolved CASSANDRA-10896.
--------------------------------------
Resolution: Fixed
This was dealt with in refactoring the upgrade tests.
> Fix skipping logic on upgrade tests in dtest
> --------------------------------------------
>
> Key: CASSANDRA-10896
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10896
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jim Witschey
> Assignee: DS Test Eng
> Labels: dtest
> Fix For: 3.0.x
>
>
> This will be a general ticket for upgrade dtests that fail because of bad
> logic surrounding skipping tests. We need a better system in place for
> skipping tests that are not intended to work on certain versions of
> Cassandra; at present, we run the upgrade tests with {{SKIP=false}} because,
> again, the built-in skipping logic is bad.
> One such test is test_v2_protocol_IN_with_tuples:
> http://cassci.datastax.com/job/storage_engine_upgrade_dtest-22_tarball-311/lastCompletedBuild/testReport/upgrade_tests.cql_tests/TestCQLNodes3RF3/test_v2_protocol_IN_with_tuples/
> This shouldn't be run on clusters that include nodes running 3.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
