You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2019/02/05 10:56:00 UTC

[jira] [Updated] (CASSANDRA-14937) Multi-version In-JVM dtests

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

Benedict updated CASSANDRA-14937:
---------------------------------
       Resolution: Fixed
         Reviewer:   (was: Alex Petrov)
    Fix Version/s:     (was: 3.11.x)
                       (was: 3.0.x)
                       (was: 2.2.x)
                   4.0
                   3.11.5
                   3.0.19
                   2.2.15
        Reviewers: Alex Petrov
           Status: Resolved  (was: Patch Available)

Committed; Alex will be following up with changes to CircleCI to disable distributed tests for the meantime, as the issues with stability do not seem to be related to this patch.

> Multi-version In-JVM dtests
> ---------------------------
>
>                 Key: CASSANDRA-14937
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14937
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Test/dtest
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Major
>             Fix For: 2.2.15, 3.0.19, 3.11.5, 4.0
>
>
> In order to support more sophisticated upgrade tests, including complex fuzz tests that can span a sequence of version upgrades, we propose abstracting a cross-version API for the in-jvm dtests.  This will permit starting a node with an arbitrary compatible C* version, stopping the node, and restarting it with another C* version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org