cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10563) Integrate new upgrade test into dtest upgrade suite
Date Thu, 28 Jan 2016 17:29:40 GMT


Sam Tunnicliffe commented on CASSANDRA-10563:

On CASSANDRA-11087, [~thobbs] suggests

bq. Should we add a flag to the upgrade tests to control flushing before upgrading? It seems
like we want to test both behaviors (to ensure commitlog replay is also covered), but there
could easily be other legacy sstable reading bugs out there.

Which seems eminently sensible (apologies in advance if that's already on the table, I haven't
been through [~slebresne]'s dtest branch yet).

> Integrate new upgrade test into dtest upgrade suite
> ---------------------------------------------------
>                 Key: CASSANDRA-10563
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Testing
>            Reporter: Jim Witschey
>            Assignee: Jim Witschey
>            Priority: Critical
>             Fix For: 3.0.x
> This is a follow-up ticket for CASSANDRA-10360, specifically [~slebresne]'s comment here:
> These tests should be incorporated into the [{{upgrade_tests}} in dtest|].
I'll take this on; [~nutbunnies] is also a good person for it, but I'll likely get to it first.

This message was sent by Atlassian JIRA

View raw message