[
https://issues.apache.org/jira/browse/CASSANDRA-17854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603124#comment-17603124
]
Brandon Williams commented on CASSANDRA-17854:
----------------------------------------------
Pretty sure that's because it uses branches that weren't active for
CASSANDRA-17581, and our current image doesn't have a new enough JDK to break
on it, but this one does. The same issues occur when running other tests that
do this outside of docker with a new JDK.
One solution might be committing the same fix to 2.0/2.1/2.2, but it looks like
this test uses a specific version so we might have to make changes to tests as
well.
> Add JDK17 to our test docker images
> -----------------------------------
>
> Key: CASSANDRA-17854
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17854
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.x
>
>
> In preparation to support JDK 17 I want to add JDK 17 to our test images to
> enable our CIs for testing with JDK 17
>
--
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
