[
https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492263#comment-17492263
]
Ekaterina Dimitrova commented on CASSANDRA-17351:
-------------------------------------------------
Alright, so the issue with cqlshlib was that even if we test only for python 3
in 4.0 and trunk, we were trying to install futures which is a backport for
Python 2.
I removed it from requirements.txt and changed pip to pip3. Now it finished
smoothly
[here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1391/workflows/6c82d568-7da5-46db-a676-6d52f65e52d2/jobs/9016]
We don't run cqlshlib in Circle for cassandra-3.11(where I assume no changes
are needed as we run Python 2), so to test I started in Jenkins a run
[here|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1426/]
So the plan introduced stand, only with the change suggested around cqlshlib
tests for 4.0 and trunk.
I will check tomorrow how Jenkins finished and if it is fine, [~mck] as the
most involved person with images, CI, etc I will ask you to sanity check the
approach before I do changes to all branches and push CI for all branches in
both CIs as it is time and resource consuming and I don't want to push it only
to understand that it is not what we want :)
> Pip doesn't install ccm every time
> ----------------------------------
>
> Key: CASSANDRA-17351
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17351
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Urgent
> Fix For: 4.x
>
>
> In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to
> run without -e for ccm in order to address the moveable tag. That worked for
> some time until last night. I successfully retagged and now ccm is not
> re-installed in Circle CI.
> Jenkins picked stuff though. But it was acting unreliably and weird so
> rerunning now things there. Results pending.
> Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still
> pending results. I don't think this will be permanent solution and I am not
> sure whether it will affect also the previous branches in a way. We need to
> further investigate it and test.
> For now I will ask people to test with -e until we figure it out.
> CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
