[ 
https://issues.apache.org/jira/browse/CASSANDRA-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694745#comment-17694745
 ] 

Brandon Williams commented on CASSANDRA-18106:
----------------------------------------------

I have had no luck reproducing this yet.

bq. I assume it is not CASSANDRA-18258 as your previous run that failed that 
way was when CASSANDRA-18258 it was still not committed.

Indeed, it can't be CASSANDRA-18258 for that reason.  I rebased to include it 
though (because why not) and ran again with the same failures 
[here|https://app.circleci.com/pipelines/github/driftx/cassandra/874/workflows/09dd4abd-a0bb-4b03-9364-c12d84b46f65].
 I feel like there must be bad jdk interaction here somewhere, but everything 
looks correct in the logs, and it's especially strange that it fails to _stop_ 
jolokia, but all the important bits it's used for pass.

> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to