[
https://issues.apache.org/jira/browse/CASSANDRA-7327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017267#comment-14017267
]
Tyler Hobbs commented on CASSANDRA-7327:
----------------------------------------
Patches 1 and 2 look good to me.
For patch 3, can we set the system property in {{build.xml}} for all of the
unit tests, or are there tests that causes problems for?
On patch 4, we may want to check that there's not a problem with file deletion
on Windows (there always seems to be :)) /cc [~JoshuaMcKenzie]
> Reduce new CQL test time
> ------------------------
>
> Key: CASSANDRA-7327
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7327
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 2.1.0
>
> Attachments: 0001-Don-t-require-Gossiper-for-schema-changes.txt,
> 0002-Don-t-flush-schema-tables-all-the-time.txt,
> 0003-Reduce-memtable-static-initialization-time-for-tests.txt,
> 0004-Use-forkmode-once-for-cql-test.txt
>
>
> We've introduced CQL tests in the unit test suite and in particular a new
> CQLTester class meant for all those test to use. Currently, we have only 2
> test classes yet those tests takes about 20-22 seconds to run on my box. This
> is way too long.
> This issue is linked to CASSANDRA-6968, but here I'm only focusing on the CQL
> tests. Those don't load all the schema from SchemaLoader so are not directly
> targeted by CASSANDRA-6968. That said, I think most of what is done here can
> be backported to the rest of the unit tests and I'll let that to
> CASSANDRA-6968.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
