[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504896#comment-17504896 ]
Michael Semb Wever commented on CASSANDRA-17351: ------------------------------------------------ The pbr broke how the ccm script was installed. pbr is still used, but the way the ccm script is installed is reverting to the existing approach. (Thanks [~beobal] for the investigation and fix.) Committed to ccm as [dad2e4c|https://github.com/riptano/ccm/commit/dad2e4cd599b01170fc4820c5583aa54189504a7] and cassandra-test retagged. ci-cassandra.a.o main pipeline builds have been kicked off again. > 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.1 > > > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org