You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2022/05/26 18:08:00 UTC

[jira] [Comment Edited] (CASSANDRA-17656) jvm-dtest upgrade tests run all supported pairs of upgrades between from/to but does not actually test all patches from/to

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

David Capwell edited comment on CASSANDRA-17656 at 5/26/22 6:07 PM:
--------------------------------------------------------------------

in order to test the longer paths (3.0 -> 3.11 -> 4.0 -> 4.1 -> trunk) we need to improve how CI works due to the fact that these tests would be scoped to a single file/jvm which can overload the JVM and cause large delays (30s test taking 8m)


was (Author: dcapwell):
in order to test the longer paths (3.0 -> 3.11 -> 4.0 -> 4.1 -> trunk) we need to improve house CI works due to the fact that these tests would be scoped to a single file/jvm which can overload the JVM and cause large delays (30s test taking 8m)

> 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: 1h 40m
>  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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org