cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10269) Run new upgrade tests on supported upgrade paths
Date Fri, 04 Sep 2015 19:39:46 GMT


Tyler Hobbs commented on CASSANDRA-10269:

bq. The purpose of these new tests isn't clear to me anymore. Do we want to only use them
to test upgrades involving the storage engine change, or do we want to treat them as general
upgrade tests?

They're general purpose upgrade tests.  (They just happened to be particularly important after
8099 changes.)  Since it's not clear when in the future we should start running 3.0 ->
trunk upgrade tests, I'm in favor of just starting it now so that unknown problems don't build

> Run new upgrade tests on supported upgrade paths
> ------------------------------------------------
>                 Key: CASSANDRA-10269
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Jim Witschey
>            Assignee: Jim Witschey
> The upgrade dtests for 8099 backwards compatibility (originally dealt with in [this dtest
PR|] and [this JIRA ticket|])
need to be run with upgrades over the following upgrade paths:
> - 2.1 -> 3.0
> - 2.2 -> 3.0
> - 3.0 -> trunk
> There are a number of ways we could manage this. We could run the tests as part of the
normal dtest jobs in 2.1, 2.2, and 3.0, and select what version to upgrade to based on the
version of the test. We could also refactor the new upgrade tests to use the upgrade machinery
in the existing upgrade tests.
> [~philipthompson] [~rhatch] Do you have opinions? Can you think of other options?

This message was sent by Atlassian JIRA

View raw message