[
https://issues.apache.org/jira/browse/CASSANDRA-16688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350069#comment-17350069
]
Michael Semb Wever edited comment on CASSANDRA-16688 at 5/23/21, 7:23 PM:
--------------------------------------------------------------------------
To reproduce…
{code}
docker run -it apache/cassandra-testing-ubuntu2004-java11-w-dependencies
/bin/bash
git clone --single-branch --branch trunk --depth 1
https://github.com/apache/cassandra-dtest.git ~/cassandra-dtest
cd cassandra-dtest/
source ~/env3.6/bin/activate
pip3 install -r requirements.txt
{code}
The patch that has been committed to 4.0 and trunk, switches the
cassandra-dtest's requirement.txt from using
https://github.com/riptano/ccm.git@cassandra-test to using
git://github.com/riptano/ccm.git@cassandra-test for the ccm dependency. That
works the first time because the repository needs to get cloned again to switch
from one upstream URL to another. But it won't work when ccm gets re-tagged
again.
Talking with [~dcapwell], the correct approach appears to be removing the
{{`-e`}} flag from requirements.txt, so that ccm is not installed by pip in
editable mode. This will make pip install ccm fresh each time, working around
the problem (for developers and CI).
Patch:
https://github.com/apache/cassandra-dtest/compare/trunk...thelastpickle:mck/16688
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest/701/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest/701/]
and
[circleci|https://app.circleci.com/pipelines/github/michaelsembwever/cassandra?branch=mck%2F16688%2Ftrunk]
was (Author: michaelsembwever):
To reproduce…
{code}
docker run -it apache/cassandra-testing-ubuntu2004-java11-w-dependencies
/bin/bash
git clone --single-branch --branch trunk --depth 1
https://github.com/apache/cassandra-dtest.git ~/cassandra-dtest
cd cassandra-dtest/
source ~/env3.6/bin/activate
pip3 install -r requirements.txt
{code}
The patch that has been committed to 4.0 and trunk, switches the
cassandra-dtest's requirement.txt from using
https://github.com/riptano/ccm.git@cassandra-test to using
git://github.com/riptano/ccm.git@cassandra-test for the ccm dependency. That
works the first time because the repository needs to get cloned again to switch
from one upstream URL to another. But it won't work when ccm gets re-tagged
again.
Talking with [~dcapwell], the correct approach appears to be removing the
{{`-e`}} flag from requirements.txt, so that ccm is not installed by pip in
editable mode. This will make pip install ccm fresh each time, working around
the problem (for developers and CI).
Patch:
https://github.com/apache/cassandra-dtest/compare/trunk...thelastpickle:mck/16688
> CircleCI - python dtests failing because of ccm issue
> -----------------------------------------------------
>
> Key: CASSANDRA-16688
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16688
> Project: Cassandra
> Issue Type: Bug
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
>
> Circle CI fails to run dtests.
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/483/workflows/e9a5f84e-e465-40e6-92f4-08e8632edf47/jobs/4315]
> {code:java}
> Obtaining ccm from git+
> [https://github.com/riptano/ccm.git@cassandra-test#egg=ccm]
> (from -r /home/cassandra/cassandra-dtest/requirements.txt (line 9))
> Updating ./env3.6/src/ccm clone (to revision cassandra-test)
> Running command git fetch -q --tags
> WARNING: Discarding git+
> [https://github.com/riptano/ccm.git@cassandra-test#egg=ccm]
> . Command errored out with exit status 1: git fetch -q --tags Check the logs
> for full command output.
> ERROR: Could not find a version that satisfies the requirement ccm
> (unavailable)
> ERROR: No matching distribution found for ccm (unavailable)
> WARNING: You are using pip version 21.0.1; however, version 21.1.1 is
> available.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
