cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-10470) Fix likely dtest bugs in upgrade_tests
Date Thu, 08 Oct 2015 14:54:27 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paulo Motta reassigned CASSANDRA-10470:
---------------------------------------

    Assignee: Paulo Motta

> Fix likely dtest bugs in upgrade_tests
> --------------------------------------
>
>                 Key: CASSANDRA-10470
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10470
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Jim Witschey
>            Assignee: Paulo Motta
>             Fix For: 3.0.0 rc2
>
>
> These two upgrade tests fail on CassCI:
> http://cassci.datastax.com/view/Upgrades/job/storage_engine_upgrade_dtest-22_tarball-30_HEAD/44/testReport/upgrade_tests.paging_test/TestPagingDatasetChanges/test_cell_TTL_expiry_during_paging/
> http://cassci.datastax.com/view/Upgrades/job/storage_engine_upgrade_dtest-22_tarball-30_HEAD/44/testReport/upgrade_tests.cql_tests/TestCQL/counters_test/
> I believe the tests expect values to be formatted slightly differently, e.g. for values
to have type {{unicode}} instead of {{str}}. If I'm wrong and this requires more than a few
dtest fixes, this should be split out into multiple tickets.
> Once [this dtest PR|https://github.com/riptano/cassandra-dtest/pull/586] is merged, these
tests should also run with this upgrade path on normal 3.0 jobs. Until then, you can run it
with the following command:
> {code}
> SKIP=false CASSANDRA_VERSION=binary:2.2.0 UPGRADE_TO=git:cassandra-3.0 nosetests 2>&1
upgrade_tests/cql_tests.py:TestCQL.collection_indexing_test
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message