cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10799) 2 cqlshlib tests still failing with cythonized driver installation
Date Fri, 04 Dec 2015 13:11:10 GMT


Stefania commented on CASSANDRA-10799:

I've adapted the cqlshlib tests to always use the embedded driver even when there is a driver
installed. Two things to note:

* Because the location of the lib folder containing the driver zip file is calculated as relative
to {{__file__}}, the soft link created was causing problems and so I got rid of it. The reason
for this soft link was exclusively for importing cqlsh and since the renaming to
in 2.2 this is no longer necessary. However in 2.1 we cannot get rid of a soft link (or copy)
unless we rename cqlsh to and therefore I did not fix 2.1.

* If running the tests from _pylib/cqlshlib_, like we don on Jenkins, _cqlshlib_ is added
to {{sys.path}} and this caused an error when importing {{cassandra.Cluster}} due to a conflict
between the python copy module and _cqlshlib/copy.py_. This is a serious problem and I fixed
it in 2.1 as well. The only reason we don't notice when running cqlsh is that we import {{cassandra.Cluster}}
after adding cqlshlib to {{sys.path}}.

Patches and CI:


2.2 applied cleanly to 3.0 and so I did not create the patches for 3.1 and trunk but I can
do so after review is completed.

> 2 cqlshlib tests still failing with cythonized driver installation
> ------------------------------------------------------------------
>                 Key: CASSANDRA-10799
>                 URL:
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Stefania
>            Assignee: Stefania
>             Fix For: 2.2.x, 3.x
> We still have 2 cqlshlib tests failing on Jenkins:
> Locally, these tests only fail with a cythonized driver installation. If the driver is
not cythonized (installed with {{--no_extensions}}) then the tests are fine.

This message was sent by Atlassian JIRA

View raw message