[jira] [Commented] (CASSANDRA-17070) ViewComplexTest hardening

["Berenguer Blasi (Jira)" <ji...@apache.org>]

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

Berenguer Blasi commented on CASSANDRA-17070:
---------------------------------------------

Right. But it's on view creation, not the cleanup logic. Seems like a legit timeout. I've had the feeling timeouts have to be raised for some time. I still think we're good to merge. Or are you suggesting we put the cleanup back in?

{noformat}
[junit-timeout] Testcase: testUpdateWithColumnTimestampSmallerThanPkWithFlush[3](org.apache.cassandra.cql3.ViewComplexUpdatesTest):	Caused an ERROR
[junit-timeout] [localhost/127.0.0.1:43739] Timed out waiting for server response
[junit-timeout] com.datastax.driver.core.exceptions.OperationTimedOutException: [localhost/127.0.0.1:43739] Timed out waiting for server response
[junit-timeout] 	at com.datastax.driver.core.exceptions.OperationTimedOutException.copy(OperationTimedOutException.java:43)
[junit-timeout] 	at com.datastax.driver.core.exceptions.OperationTimedOutException.copy(OperationTimedOutException.java:25)
[junit-timeout] 	at com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:35)
[junit-timeout] 	at com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:293)
[junit-timeout] 	at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:58)
[junit-timeout] 	at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:45)
[junit-timeout] 	at org.apache.cassandra.cql3.CQLTester.executeNet(CQLTester.java:972)
[junit-timeout] 	at org.apache.cassandra.cql3.ViewComplexTester.createView(ViewComplexTester.java:83)
[junit-timeout] 	at org.apache.cassandra.cql3.ViewComplexUpdatesTest.testUpdateWithColumnTimestampSmallerThanPk(ViewComplexUpdatesTest.java:224)
[junit-timeout] 	at org.apache.cassandra.cql3.ViewComplexUpdatesTest.testUpdateWithColumnTimestampSmallerThanPkWithFlush(ViewComplexUpdatesTest.java:207)
[junit-timeout] Caused by: com.datastax.driver.core.exceptions.OperationTimedOutException: [localhost/127.0.0.1:43739] Timed out waiting for server response
[junit-timeout] 	at com.datastax.driver.core.RequestHandler$SpeculativeExecution.onTimeout(RequestHandler.java:979)
[junit-timeout] 	at com.datastax.driver.core.Connection$ResponseHandler$1.run(Connection.java:1636)
[junit-timeout] 	at com.datastax.shaded.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:663)
[junit-timeout] 	at com.datastax.shaded.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:738)
[junit-timeout] 	at com.datastax.shaded.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:466)
[junit-timeout] 	at com.datastax.shaded.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
[junit-timeout] 	at java.lang.Thread.run(Thread.java:748)
{noformat}


> ViewComplexTest hardening
> -------------------------
>
>                 Key: CASSANDRA-17070
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17070
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Test/unit
>            Reporter: Berenguer Blasi
>            Assignee: Berenguer Blasi
>            Priority: Normal
>             Fix For: 4.0.x, 4.x
>
>
> I have seen a number of times already the {{ViewComplexTest}} family timeout on test method teardown. This leaves a dirty env behind triggering the following test methods to fail on it. This ticket aims at hardening them.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org