[
https://issues.apache.org/jira/browse/CASSANDRA-17656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545164#comment-17545164
]
David Capwell commented on CASSANDRA-17656:
-------------------------------------------
think we came to agreement!!! upgrades method now does the following
{code}
upgradesTo(from, CURRENT);
upgradesFrom(CURRENT, to);
{code}
and added the 2 new methods upgradesTo (upgrade all paths where from changes
but to is fixed) and upgradesFrom (upgrade all paths where too changes but from
is fixed); this allows test authors to switch back to older logic if desired,
but keeps the default focused on CURRENT
> jvm-dtest upgrade tests run all supported pairs of upgrades between from/to
> but does not actually test all patches from/to
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17656
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17656
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.1.x
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> The current upgrade from/to logic is based off a list filter on from/to
> pairs, and runs the test multiple times for each pair; this does not actually
> validate that the different paths upgrade cleanly.
> Instead, we need to test each supported path; example 3.0 -> 4.2
> {code}
> 3.0.28 -> [4.2]
> 3.0.28 -> [3.11.14, 4.2]
> 3.0.28 -> [4.1-alpha1, 4.2]
> 3.0.28 -> [4.0.5, 4.2]
> 3.0.28 -> [3.11.14, 4.1-alpha1, 4.2]
> 3.0.28 -> [3.11.14, 4.0.5, 4.2]
> 3.0.28 -> [4.0.5, 4.1-alpha1, 4.2]
> 3.0.28 -> [3.11.14, 4.0.5, 4.1-alpha1, 4.2]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
