[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352283#comment-17352283
]
Berenguer Blasi commented on CASSANDRA-16672:
-
I was about to commit that CCM change from CASSANDRA-16644 but there are some
build problems today so I'll hold off to next week #justfyi
> 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: 3.0.25, 3.11.11, 4.0-rc2, 4.0, 4.1
>
>
> 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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350924#comment-17350924
]
Berenguer Blasi commented on CASSANDRA-16672:
-
Yep the ccm change has been in my TODO list. I was leaving some breathing space
to the ccm retagging. I prefer to go one change at a time as it was the first
time I was retagging ccm.
> 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: 3.0.25, 3.11.11, 4.0-rc2, 4.0, 4.1
>
>
> 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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350528#comment-17350528
]
Ekaterina Dimitrova commented on CASSANDRA-16672:
-
I think now we can commit it and retag when we close CASSANDRA-16688.
It is correction of the debug messages so I think it should be harmless if I
don't miss anything. Thank you
> 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: 3.0.25, 3.11.11, 4.0-rc2, 4.0, 4.1
>
>
> 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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350247#comment-17350247
]
Berenguer Blasi commented on CASSANDRA-16672:
-
[~e.dimitrova] the only reason that CCM patch was not committed yet is that I
am going one step at a time, nothing else.
As per the new failure I struggle to make sense of it. As I tested it on circle
and it worked. Looking at some dtest job in circle we can see the right SHA and
not the tag are being pulled indeed:
{noformat}
Obtaining ccm from git+https://github.com/riptano/ccm.git#egg=ccm (from -r
/home/cassandra/cassandra-dtest/requirements.txt (line 9))
Updating ./env3.6/src/ccm clone
Running command git fetch -q --tags
Running command git reset --hard -q 435f3210e16d0b648fbf33d6390d5ab4c9e630d4
{noformat}
> 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: 3.0.25, 3.11.11, 4.0-rc2, 4.0, 4.1
>
>
> 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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349481#comment-17349481
]
Ekaterina Dimitrova commented on CASSANDRA-16672:
-
[~bereng], I think the latest ccm patch which triggered you to see retag hasn't
been recently is still not committed. [~dcapwell] found a workaround which I
plan to ninja fix until Monday when we can commit that patch (want to
double-check with you whether it should be really committed or you had some
concerns), retag CCM and rebuild the docker image (I am positive that will
solve the problem). I am also not sure whether I will have the rights to push a
new image on docker hub.
> 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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349461#comment-17349461
]
Ekaterina Dimitrova commented on CASSANDRA-16672:
-
CASSANDRA-16688 ticket opened. Thinking out loud, I guess there are some
specifics around the tags and the CI was run on a custom branch, probably so
not being able to catch this issue. Let's see whether the rebuild will help
> 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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349434#comment-17349434
]
David Capwell commented on CASSANDRA-16672:
---
Any idea why the following is happening?
{code}
bash-4.2$ pip3 install --upgrade
git+https://github.com/riptano/ccm.git@cassandra-test#egg=ccm
Collecting ccm from
git+https://github.com/riptano/ccm.git@cassandra-test#egg=ccm
Cloning https://github.com/riptano/ccm.git (to cassandra-test) to
/tmp/pip-build-zytofrkv/ccm
error: RPC failed; curl 56 TCP connection reset by peer
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
Command "git clone -q https://github.com/riptano/ccm.git
/tmp/pip-build-zytofrkv/ccm" failed with error code 128 in None
You are using pip version 9.0.1, however version 21.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
{code}
https://app.circleci.com/pipelines/github/dcapwell/cassandra/921/workflows/3cae536f-f429-40e6-b739-9212b203cd58/jobs/5578
python dtest builds are all failing to checkout ccm
> 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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348207#comment-17348207
]
Michael Semb Wever commented on CASSANDRA-16672:
+1
> 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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348206#comment-17348206
]
Berenguer Blasi commented on CASSANDRA-16672:
-
Results
||Branch||Jenkins||Circle||Comments||
|Trunk| [OK|https://ci-cassandra.apache.org/job/Cassandra-devbranch/780/] | OK
[j11|https://app.circleci.com/pipelines/github/bereng/cassandra/302/workflows/f525aee1-96e5-4d1e-8191-4d46c16bf77c]
&
[j8|https://app.circleci.com/pipelines/github/bereng/cassandra/302/workflows/cc29c727-b44a-4e2f-8ebd-c065453c15ca]|Flakiness
on j8 upgrade tests|
|4.0|[OK|https://ci-cassandra.apache.org/job/Cassandra-devbranch/788/] after
several runs|OK
[j11|https://app.circleci.com/pipelines/github/bereng/cassandra/303/workflows/ad58fcbd-5ec1-4283-b8fd-78fb5e2a26ce]
[j8|https://app.circleci.com/pipelines/github/bereng/cassandra/303/workflows/e1286e99-9467-44b1-8bca-421c2d8f440c]||
|3.11|Some
[diffs|https://ci-cassandra.apache.org/job/Cassandra-devbranch/786/]|[OK|https://app.circleci.com/pipelines/github/bereng/cassandra/304/workflows/c12ad6a1-82fe-42ff-8b22-1e3e97b2b49d]|udt
failures repro locally with old and new ccm|
|3.0|Many
[diffs|https://ci-cassandra.apache.org/job/Cassandra-devbranch/787/]|[OK|https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-16672-3.0]|udt
failures probably same as above|
So I think there's nothing obvious broken and we can retag ccm.
> 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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348098#comment-17348098
]
Berenguer Blasi commented on CASSANDRA-16672:
-
Circle:
- [Trunk|https://github.com/bereng/cassandra/tree/CASSANDRA-16672-trunk]:
[j11|https://app.circleci.com/pipelines/github/bereng/cassandra/302/workflows/f525aee1-96e5-4d1e-8191-4d46c16bf77c]
&
[j8|https://app.circleci.com/pipelines/github/bereng/cassandra/302/workflows/cc29c727-b44a-4e2f-8ebd-c065453c15ca]
> 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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17347611#comment-17347611
]
Berenguer Blasi commented on CASSANDRA-16672:
-
Results are a bit noisy... I think I'll run them against circle to
doublecheck...
> 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
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346588#comment-17346588
]
Berenguer Blasi commented on CASSANDRA-16672:
-
CI runs:
- Trunk:
https://github.com/apache/cassandra-dtest/compare/trunk...bereng:CASSANDRA-16672?expand=1
- 4.0 tbd
- 3.11 tbd
- 3.0 tbd
> 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
