[
https://issues.apache.org/jira/browse/CASSANDRA-18396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18396:
------------------------------------------
Fix Version/s: 3.0.29
3.11.15
5.0
4.1.2
4.0.10
(was: 3.0.x)
(was: 3.11.x)
(was: 5.x)
(was: 4.0.x)
(was: 4.1.x)
Source Control Link:
https://github.com/apache/cassandra-dtest/commit/5715e36a71e261408dfd22f74f1f4b8df3983659
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Dtests marked with @ported_to_in_jvm can be skipped since 4.1
> -------------------------------------------------------------
>
> Key: CASSANDRA-18396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18396
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 3.0.29, 3.11.15, 5.0, 4.1.2, 4.0.10
>
>
> During the CASSANDRA-15536 epic we ported multiple Python dtests to in-JVM
> dtests.
> The ported Python dtests are still present but marked with a new
> {{@ported_to_in_jvm}} annotation. JVM dtests didn't support vnodes at that
> time, so when a Python dtest is marked with that annotation it's only run for
> vnodes config, whereas it's skipped if vnodes are off.
> However, we have had support for vnodes on JVM dtests since 4.1. Thus, I
> think we should modify the {{@ported_to_in_jvm}} annotation to also skip
> configs with vnodes if all the nodes are in 4.1 or later.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
