[
https://issues.apache.org/jira/browse/CASSANDRA-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694204#comment-17694204
]
Brandon Williams commented on CASSANDRA-18106:
----------------------------------------------
Interesting, they [failed
again|https://app.circleci.com/pipelines/github/driftx/cassandra/863/workflows/b154a40b-891a-42d4-9b4e-8e83db4881b3/jobs/12465/tests].
Odd since they passed
[before|https://app.circleci.com/pipelines/github/driftx/cassandra/863/workflows/3d4b4877-d2e3-4dd3-81bf-cf2a0874f278]
although that was the j11 tests. I'll take a look.
bq. I had to remove the "-e" from requirements.txt to be able to install your
branch locally. Not sure why
Well to be honest, I'm not sure why it's there, I just followed what the
comment said to do..which is from you :)
> Update CCM for JDK17 and revise current JDK detection strategy
> --------------------------------------------------------------
>
> Key: CASSANDRA-18106
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18106
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.x
>
>
> As part of CASSANDRA-16895 initial POC an initial version of CCM patch was
> created. This needs to be revisited and reviewed
> Recently we closed CASSANDRA-18039 which brought questions, probably we need
> to revise how we detect JDK versions in CCM and whether it is correct. To the
> best of my knowledge there are certain tests in the repo around that and they
> pass so my guess is we need to revise just the strategy and maybe document it
> explicitly or consider if we want any changes to be applied. Also, we need to
> be careful with breaking changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
