[ 
https://issues.apache.org/jira/browse/CALCITE-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142187#comment-17142187
 ] 

Ruben Q L commented on CALCITE-2442:
------------------------------------

With the current master, I still see a random initializationError on Cassandra 
tests:
{code}
17:27:01 > Task :cassandra:test
17:27:01 FAILURE   0.0sec, 
org.apache.calcite.test.CassandraAdapterDataTypesTest > initializationError
17:27:01     com.datastax.driver.core.exceptions.OperationTimedOutException: 
[localhost/127.0.0.1:9142] Timed out waiting for server response
17:27:01         at 
com.datastax.driver.core.exceptions.OperationTimedOutException.copy(OperationTimedOutException.java:43)
17:27:01         at 
com.datastax.driver.core.exceptions.OperationTimedOutException.copy(OperationTimedOutException.java:25)
17:27:01         at 
com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:35)
17:27:01         at 
com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:293)
17:27:01         at 
com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:58)
17:27:01         at 
com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:39)
17:27:01         at 
org.cassandraunit.utils.CqlOperations.lambda$execute$0(CqlOperations.java:16)
17:27:01         at 
org.cassandraunit.utils.CqlOperations.lambda$dropKeyspace$3(CqlOperations.java:29)
17:27:01         at 
org.cassandraunit.CQLDataLoader.initKeyspaceContext(CQLDataLoader.java:51)
17:27:01         at org.cassandraunit.CQLDataLoader.load(CQLDataLoader.java:30)
17:27:01         at 
org.apache.calcite.test.CassandraAdapterDataTypesTest.load(CassandraAdapterDataTypesTest.java:53)
17:27:01         Caused by: 
com.datastax.driver.core.exceptions.OperationTimedOutException: 
[localhost/127.0.0.1:9142] Timed out waiting for server response
17:27:01             at 
com.datastax.driver.core.RequestHandler$SpeculativeExecution.onTimeout(RequestHandler.java:954)
17:27:01             at 
com.datastax.driver.core.Connection$ResponseHandler$1.run(Connection.java:1575)
17:27:01             at 
io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:625)
17:27:01             at 
io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:700)
17:27:01             at 
io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:428)
17:27:01             at 
io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
17:27:01             at java.lang.Thread.run(Thread.java:748)
17:27:01 
17:27:01 FAILURE  12.0sec,    1 completed,   1 failed,   0 skipped, 
org.apache.calcite.test.CassandraAdapterDataTypesTest
{code}

Is anybody else experiencing the same thing?

> Cassandra unit test intermittent failures
> -----------------------------------------
>
>                 Key: CALCITE-2442
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2442
>             Project: Calcite
>          Issue Type: Bug
>          Components: cassandra-adapter
>            Reporter: Andrei Sereda
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.22.0
>
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
>
> We have noticed that there are failures due to : 
> # Wrong parsing of new [JDK version scheme|http://openjdk.java.net/jeps/223] 
> (by calcite and cassandra dependencies like jamm). {{10-ea}} vs {{10.0.2}} 
> # Cassandra startup timeout on Linux Jenkins CI server. Contrary to github 
> travis CI (the one which validates PRs), it takes about 20s for embedded 
> cassandra to start (still under investigation).
> # [~Sergey Nuyanzin] reported that 
> [CassandraUnit|https://github.com/jsevellec/cassandra-unit] leaves 
> {{.toDelete}} folder in maven module folder ({{cassandra/}}) rather than 
> {{target/}} where all build and temporary files should be located. Not a 
> failure but annoyance. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to