[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349447#comment-17349447
]
Ekaterina Dimitrova commented on CASSANDRA-16672:
-------------------------------------------------
[~adelapena] mentioned he had that issue too. I haven't tested it myself but if
you say you see it too, it means it wasn't something random.
Andres managed also to reproduce it locally running {{pip install -r
requirements.txt}} in his local python venv. It works after dropping the old
copy of the ccm repo that he had in his venv, on the {{src}} dir of the venv.
As for CircleCI, it says here that the dependencies are already installed on
the Docker image:
[https://github.com/apache/cassandra/blob/trunk/.circleci/config-2_1.yml#L1109-L1117]
Might be that we need to rebuild the docker image, not sure. As the retagging
is just change of hash, no new dependencies added. Also, I see CI being run
successfully before the commit but seems Berenguer cleaned already his repo and
I can't see the commits to verify if something has been missing there.
> Retag ccm
> ---------
>
> Key: CASSANDRA-16672
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16672
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/python
> Reporter: Berenguer Blasi
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0-rc2, 4.0, 3.0.x, 3.11.x, 4.x
>
>
> CCM repro's trunk is several commits ahead from {{cassandra-test}} tag.
> Probably an oversight but retagging needs CI to be ran just to make sure
> nothing broke in between.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
