[
https://issues.apache.org/jira/browse/CASSANDRA-19026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787129#comment-17787129
]
Jacek Lewandowski edited comment on CASSANDRA-19026 at 11/17/23 10:40 AM:
--------------------------------------------------------------------------
I've compared locally the time of running `ant test` target. Here the results:
||Branch || Total time || Output size || Test cases time ||
|{{cassandra-4.0}} | 92m 55s | 468M | 75m 1s |
|{{CASSANDRA-19026-4.0}} | 71m 51s (-22%) | 391M (-16 %) |
54m 42s |
was (Author: jlewandowski):
I've compared locally the time of running `ant test` target. Here the results:
||Branch || Total time || Output size || Test cases time ||
|{{cassandra-4.0}} | 92m 55s | 468M | 75m 1s |
|{{CASSANDRA-19026-4.0}} | 71m 51s | 391M | 54m 42s |
> Do not drop CQLTester.KEYSPACE content in @After asynchronously
> ---------------------------------------------------------------
>
> Key: CASSANDRA-19026
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19026
> Project: Cassandra
> Issue Type: Task
> Components: Test/unit
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.1
>
>
> CASSANDRA-18710 showed that removal of tables, views, functions, etc. in
> {{@After}} method asynchronously may span the next test case and modify that
> test behaviour in some unexpected way
> Concretely, {{@After}} method includes dropping {{KEYSPACE_PER_TEST}}
> synchronously and the whole content of {{KEYSPACE}} asynchronously. I don't
> see a reason for dropping the content of {{KEYSPACE}} after each test because
> that keyspace is not expected to be clean for each test case. It is the case
> for {{KEYSPACE_PER_TEST}}. Therefore I propose removal of that async cleanup
> of {{KEYSPACE}} after each test case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
