cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7327) Reduce new CQL test time
Date Wed, 04 Jun 2014 16:09:02 GMT


Sylvain Lebresne commented on CASSANDRA-7327:

That last exception is likely just do to me forgetting to synchronize the {{mergeSchemaInternal}}.
Attaching (and pushed to the previous branch) a new commit to fix that.

bq. can we set the system property in build.xml for all of the unit tests

Absolutely, I merely putted it when I had tested it, but it was definitively meant to be use
for all tests. Newly attached commit moves it.

> Reduce new CQL test time
> ------------------------
>                 Key: CASSANDRA-7327
>                 URL:
>             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

View raw message