[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17351: --- Resolution: Fixed Status: Resolved (was: Open) > 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
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Resolution: (was: Fixed) Status: Open (was: Resolved) > 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
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Fix Version/s: 4.1 (was: 4.x) > 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
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Source Control Link: https://github.com/riptano/ccm/commit/7e5ff6af02ac74c32c4380e1d1690b23e2a2c334 Resolution: Fixed Status: Resolved (was: Ready to Commit) > 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
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Reviewers: Ekaterina Dimitrova, Michael Semb Wever, Sam Tunnicliffe Status: Review In Progress (was: Patch Available) > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[
https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17351:
Test and Documentation Plan:
[https://app.circleci.com/pipelines/github/beobal/cassandra?branch=cci%2Ftrunk&filter=all]
Pipeline 386 was run when the tag pointed at
{{{}dcce52eec82a912c3b799590229e332a42affd0b{}}}. If you drill into
{{j8_separate_tests -> j8_cqlsh-dtests-py38-no-vnodes (or one of the other
similar steps) -> Configure virtualenv and python Dependencies}} (edited)
We can see this:
{code:java}
Resolved https://github.com/beobal/ccm.git
to commit dcce52eec82a912c3b799590229e332a42affd0b
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1290...{code}
Pipeline 387 was run after retagging, but without changing anything on the
Cassandra, Circle or dtest side. Following the same path shows:
{code:java}
Resolved https://github.com/beobal/ccm.git
to commit 180f2879ffce121f102f26d16883693c01f3c9c8{code}
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1291...
so _just_ moving the tag causes the version bump from {{3.1.6.dev1290}} to
{{3.1.6.dev1291}}
was:
[https://app.circleci.com/pipelines/github/beobal/cassandra?branch=cci%2Ftrunk&filter=all]
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921950420359]
pipeline 386 was run when the tag pointed at
{{{}dcce52eec82a912c3b799590229e332a42affd0b{}}}. If you drill into
{{j8_separate_tests -> j8_cqlsh-dtests-py38-no-vnodes (or one of the other
similar steps) -> Configure virtualenv and python Dependencies}} (edited)
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921981105489]
you can see this:
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921995076269]
Resolved [https://github.com/beobal/ccm.git]
to commit dcce52eec82a912c3b799590229e332a42affd0b
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1290...
[9:20|https://the-asf.slack.com/archives/C0369H83D1T/p1646922009393759]
Pipeline 387 was run after retagging, but without changing anything on the C*,
Circle or dtest side. Following the same path shows:
[9:20|https://the-asf.slack.com/archives/C0369H83D1T/p1646922028259079]
Resolved [https://github.com/beobal/ccm.git]
to commit 180f2879ffce121f102f26d16883693c01f3c9c8
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1291...
[9:22|https://the-asf.slack.com/archives/C0369H83D1T/p1646922124340229]
so _just_ moving the tag causes the version bump from {{3.1.6.dev1290}} to
{{3.1.6.dev1291}}
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Status: Ready to Commit (was: Review In Progress) > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[
https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17351:
Authors: Michael Semb Wever, Sam Tunnicliffe (was:
Ekaterina Dimitrova)
Test and Documentation Plan:
[https://app.circleci.com/pipelines/github/beobal/cassandra?branch=cci%2Ftrunk&filter=all]
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921950420359]
pipeline 386 was run when the tag pointed at
{{{}dcce52eec82a912c3b799590229e332a42affd0b{}}}. If you drill into
{{j8_separate_tests -> j8_cqlsh-dtests-py38-no-vnodes (or one of the other
similar steps) -> Configure virtualenv and python Dependencies}} (edited)
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921981105489]
you can see this:
[9:19|https://the-asf.slack.com/archives/C0369H83D1T/p1646921995076269]
Resolved [https://github.com/beobal/ccm.git]
to commit dcce52eec82a912c3b799590229e332a42affd0b
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1290...
[9:20|https://the-asf.slack.com/archives/C0369H83D1T/p1646922009393759]
Pipeline 387 was run after retagging, but without changing anything on the C*,
Circle or dtest side. Following the same path shows:
[9:20|https://the-asf.slack.com/archives/C0369H83D1T/p1646922028259079]
Resolved [https://github.com/beobal/ccm.git]
to commit 180f2879ffce121f102f26d16883693c01f3c9c8
...
Successfully installed cassandra-driver-3.24.0 ccm-3.1.6.dev1291...
[9:22|https://the-asf.slack.com/archives/C0369H83D1T/p1646922124340229]
so _just_ moving the tag causes the version bump from {{3.1.6.dev1290}} to
{{3.1.6.dev1291}}
Status: Patch Available (was: In Progress)
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Fix Version/s: 4.x > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17351: Change Category: Quality Assurance Complexity: Normal Component/s: CI Priority: Urgent (was: Normal) Status: Open (was: Triage Needed) > 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 > > 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
