[ https://issues.apache.org/jira/browse/JAMES-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023915#comment-15023915 ]
Matthieu Baechler commented on JAMES-1635: ------------------------------------------ Let throw some figures : on our CI server, the timings for cassandra related maven tasks are : [INFO] Apache James :: Mailbox :: Cassandra ............... SUCCESS [08:02 min] [INFO] Apache James MPT Imap Mailbox - Cassandra .......... SUCCESS [12:15 min] [INFO] Apache James :: Server :: Data :: Cassandra Persistence SUCCESS [ 48.700 s] It's why we set timeout to 30 minutes, it's about 3 times the longer test suite execution time. I understand that it can be slower on older/slower hardware and we can change this value to 3600. What times do you experience on your hardware ? About the suggested solution : 1/ using a new keyspace for each test : I tried this one, it's at least 3 times slower than wiping tables, it looks like table creation is rather slow on Cassandra 2/ use parallel execution : it will load your hardware even harder, It can help on multicore + SSD, but I'm not sure it will help on older hardware, and it needs 1/ to work. 3/ remove some MPT tests : it's probably something to investigate About total execution time, we have 35:32 min on our hardware, it's slow but it's not 2h+ > Can not run unit tests > ---------------------- > > Key: JAMES-1635 > URL: https://issues.apache.org/jira/browse/JAMES-1635 > Project: James Server > Issue Type: Bug > Affects Versions: Trunk > Reporter: Tellier Benoit > Fix For: Trunk > > > I got this exception, either in cassandra mailbox and Cassandra backend ; > For example : > initializeTypesShouldCreateTheTypes(org.apache.james.backends.cassandra.init.CassandraTypeProviderTest) > Time elapsed: 14.353 sec <<< FAILURE! > java.lang.AssertionError: Cassandra daemon did not start within timeout > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:130) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:85) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:64) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:56) > at > org.cassandraunit.utils.EmbeddedCassandraServerHelper.startEmbeddedCassandra(EmbeddedCassandraServerHelper.java:52) > at > org.apache.james.backends.cassandra.CassandraCluster.<init>(CassandraCluster.java:57) > at > org.apache.james.backends.cassandra.CassandraCluster.create(CassandraCluster.java:51) > at > org.apache.james.backends.cassandra.init.CassandraTypeProviderTest.setUp(CassandraTypeProviderTest.java:66) > I increased the max retry count of the Cassandra cluster but it does not > solve my problem. > It really slow down my worlflow... -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org