[
https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488519#comment-17488519
]
Ekaterina Dimitrova commented on CASSANDRA-17351:
-------------------------------------------------
I see Jenkins and Circle CI run absolutely the same command:
_pip3 install --exists-action w --upgrade -r ~/cassandra-dtest/requirements.txt_
Then in my mind the only difference is versions.
Seems to me Jenkins uses 21.2.4 for pip3 and 20.8.1 for virtualenv, but
CircleCI uses different ones - 21.0.1 for pip and 20.4.2 for virtualenv.
I see different venv used, [~mck], is this intentional?
> 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
> 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]
