[ https://issues.apache.org/jira/browse/CASSANDRA-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694188#comment-17694188 ]
Ekaterina Dimitrova commented on CASSANDRA-18106: ------------------------------------------------- In the last run pushed DTests seems to have failed with JDK11, something weird with Jolokia? Can you, please, maybe rerun them? CASSANDRA-18258 got committed today. I can confirm I tried locally with your CCM branch to start node, run some tests. As expected, it correctly works with 17 with trunk builds 11 and 17. I am +1 on clean CI, thanks PS I had to remove the "-e" from requirements.txt to be able to install your branch locally. Not sure why > 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