cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10269) Run new upgrade tests on supported upgrade paths
Date Fri, 04 Sep 2015 16:01:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730988#comment-14730988
] 

Sylvain Lebresne commented on CASSANDRA-10269:
----------------------------------------------

bq. We could run the tests as part of the normal dtest jobs in 2.1, 2.2, and 3.0

I'll note that it would be my preference to split them from the normal dtest if that's not
too much trouble, mostly because those test takes time and having the "normal" dtests separated
allows to get the feedback on them more quickly. Also, regarding the tests ran on user's branch,
I don't it's worth running both 2.1->3.0 and 2.2->3.0. It sufficiently unlikely to get
difference between the two that running it every time on every users branch feels like a wast
of resources to me.

> Run new upgrade tests on supported upgrade paths
> ------------------------------------------------
>
>                 Key: CASSANDRA-10269
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10269
>             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|https://github.com/riptano/cassandra-dtest/pull/471] and [this JIRA ticket|https://issues.apache.org/jira/browse/CASSANDRA-9893])
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
(v6.3.4#6332)

Mime
View raw message