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

Paulo Motta commented on CASSANDRA-10753:
-----------------------------------------

bq. By the way, do you know which version it is? I could not even find commit 
3f15725 on any branch in the driver repository. Shouldn't we upgrade to a later 
and more official version instead?

I think this was a custom build before c5354507aab471bd9f9f017138302693ea9e48ed 
was merged into master. I guess we should be safe to update to the released 
3.0.0 tag. There are some [instructions 
here|https://github.com/datastax/python-driver/blob/master/README-dev.rst#packaging-for-cassandra]
 here for creating the artifact.

bq. I also started noticing some timeout failures in the cqlshlib tests, on all 
branches, when dropping keyspaces. Do you think this is normal?

That's strange, it shouldn't take that long with such a small amount of data 
even on HDDs IMO. Maybe it's a ccm problem? CASSANDRA-8816 reported slowness on 
keyspace drop on Windows, so maybe you could run those tests and check if 
they're failing in your machine? Is it possible to enable tracing on drop 
keyspace statements? It would may be nice see what's making it so slow.

bq. I'll start the dtests as soon as CASSCI is back.

Seems cassci is still not back, so we can restart it after it's back.

> Fix completion problems breaking clqshlib tests
> -----------------------------------------------
>
>                 Key: CASSANDRA-10753
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10753
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stefania
>            Assignee: Stefania
>             Fix For: 3.0.x
>
>
> The recent changes in the python driver APIs have caused some completion 
> problems as indicated by 2 of these failing tests:
> http://cassci.datastax.com/job/trunk_cqlshlib/579/testReport/
> The third failing test, {{test_timestamp_output}}, has been failing for some 
> time due to uncertainty on what to do regarding timezone conversion but it 
> too can be changed to reflect the fact that we convert the timestamp to UTC.
> Finally, {{max_window_size_seconds}} was recently added to the compaction 
> properties and this caused 2 more tests to fail. It cannot be seen on Jenkins 
> because of the relative import problem introduced by CASSANDRA-9304. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to