[
https://issues.apache.org/jira/browse/CASSANDRA-14931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16748132#comment-16748132
]
Benedict commented on CASSANDRA-14931:
--------------------------------------
Thanks for the review. I've committed to
[2.2|https://github.com/apache/cassandra/commit/fdb17350109d8cf4d5a4b1deab0220fd271acc63]
[3.0|https://github.com/apache/cassandra/commit/459945bcf4f029f068199cae1418dd3bc2fc01ce]
[3.11|https://github.com/apache/cassandra/commit/2d05bff0ba4016229ecfd3f05f4c0e1a137b55f4]
and
[4.0|https://github.com/apache/cassandra/commit/2f2455be5f3aae04b6247dfca268648a65fc3adb]
> Backport In-JVM dtests to 2.2, 3.0 and 3.11
> -------------------------------------------
>
> Key: CASSANDRA-14931
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14931
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest
> Reporter: Benedict
> Assignee: Benedict
> Priority: Major
> Fix For: 2.2.14, 3.0.18, 3.11.4
>
>
> The In-JVM dtests are of significant value, and much of the testing we are
> exploring with it can easily be utilised on all presently maintained
> versions. We should backport the functionality to at least 3.0.x and 3.11.x
> - and perhaps even consider 2.2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
