[
https://issues.apache.org/jira/browse/CASSANDRA-20509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945719#comment-17945719
]
Dmitry Konstantinov commented on CASSANDRA-20509:
-------------------------------------------------
[https://github.com/apache/cassandra-dtest/pull/277]
As an option I have altered the test to check a bit different thing: to
validate do we have a direct memory allocation proportional to the request size
for the second big request. So, it is a kind of black box testing that we do
not have a direct memory leak per request.
500 repeated runs of the test are passed for the change (thanks to
[~smiklosovic] for running it):
*
[https://app.circleci.com/pipelines/github/instaclustr/cassandra/5753/workflows/9204b490-a4bc-40b2-a4ea-d7a1362aa478]
*
[https://app.circleci.com/pipelines/github/instaclustr/cassandra/5753/workflows/eecdeb23-5710-4e61-8a39-e8a9d1b2f217]
> Test failure: largecolumn_test.TestLargeColumn.test_cleanup
> -----------------------------------------------------------
>
> Key: CASSANDRA-20509
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20509
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: Dmitry Konstantinov
> Assignee: Dmitry Konstantinov
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/2086/#showFailuresLink
> TestLargeColumn.test_cleanup starts to fail since 2086 build.
> It was flaky some time ago but I fixed it and it was stable: CASSANDRA-19702
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
