cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12379) CQLSH completion test broken by #12236
Date Fri, 05 Aug 2016 14:40:20 GMT


Philip Thompson commented on CASSANDRA-12379:

Ahh, I didn't realize we already require setting enable_UDF. We'll go ahead and make the change

> CQLSH completion test broken by #12236
> --------------------------------------
>                 Key: CASSANDRA-12379
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Stefania
> The commit of CASSANDRA-12236 appears to have broken [cqlsh completion tests|,label=ctool-lab/testReport/junit/cqlshlib.test.test_cqlsh_completion/TestCqlshCompletion/test_complete_in_create_columnfamily/].
For the error message I suspect this may have to do with something like the test comparing
the completion output to what DESCRIBE shows and the later now doesn't include the {{cdc}}
option by default.
> Anyway, I'm not really familiar with cqlsh completion nor it's test so I'm not sure what's
the best option. I don't think we want to remove {{cdc}} from completion so I suspect we want
to either special case the test somehow (no clue how to do that), or make the test run with
cdc enabled so it doesn't complain (which I think mostly apply a change to the CI environment
since it seems the tests themselves don't spin up the cluster).
> Anyway, pushing that fix to someone else as I'm not competent here and I have't even
be able to run those cqlsh test so far (getting stuck at the test telling me that "No appropriate
python interpreter found", even though I totally have an appropriate interpreter and cqlsh
works perfectly if I execute it directly). 

This message was sent by Atlassian JIRA

View raw message