You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2019/01/15 19:18:00 UTC
[jira] [Commented] (CASSANDRA-14931) Backport In-JVM dtests to 2.2,
3.0 and 3.11
[ https://issues.apache.org/jira/browse/CASSANDRA-14931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743318#comment-16743318 ]
Benedict commented on CASSANDRA-14931:
--------------------------------------
I've force-pushed all branches, which are fresh cherry-picks of all of the relevant commits. It would be great if we could get these in before they go stale, although rebasing should be easier now that I have isolated cherry-picks for each branch.
I've confirmed no (apparent) leaks on any of the versions, although I have not as-yet looked into native memory leaks.
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org