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

Sam Tunnicliffe commented on CASSANDRA-10186:
---------------------------------------------

Any idea why that regression only appeared in build #108? The changes relating 
to multiple secondary indexes were committed several days earlier & the test 
had been passing. I don't see anything in the commit that triggered build #108 
that would cause it.

> Windows dtest 3.0: schema_metadata_test.py:TestSchemaMetadata.indexes_test 
> fails
> --------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10186
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10186
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Joshua McKenzie
>            Assignee: Paulo Motta
>              Labels: Windows
>             Fix For: 3.0.x
>
>
> {noformat}
> ERROR: indexes_test (schema_metadata_test.TestSchemaMetadata)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "c:\src\cassandra-dtest\schema_metadata_test.py", line 660, in 
> indexes_test
>     verify_indexes_table(self.cluster.version(), self.cluster.version(), 
> 'ks', self.session)
>   File "c:\src\cassandra-dtest\schema_metadata_test.py", line 30, in 
> verify_indexes_table
>     meta = session.cluster.metadata.keyspaces[keyspace].indexes[index_name]
> KeyError: 'idx__test_indexes'
> -------------------- >> begin captured logging << --------------------
> dtest: DEBUG: removing ccm cluster test at: c:\temp\dtest-h2pni_
> dtest: DEBUG: clearing ssl stores from [c:\temp\dtest-h2pni_] directory
> dtest: DEBUG: cluster ccm directory: c:\temp\dtest-yb4kzh
> --------------------- >> end captured logging << ---------------------
> {noformat}
> History consistent. Reproduces locally.



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

Reply via email to