[ https://issues.apache.org/jira/browse/CASSANDRA-18247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ekaterina Dimitrova updated CASSANDRA-18247: -------------------------------------------- Test and Documentation Plan: *Summary:* * Added separate CircleCI configuration files for JDK11+17 plus created a respective generate_11_and_17.sh script. The differentiator for all new files is they all end up with "_11_and_17" suffix as part of their names. The new script operates the new config files in the way generate.sh operates on the old JDK8+11 configuration files. Why I chose to do it that way? - I believe this will make it easy when the time to switch to 11+17 come. * Updated the readme. I would appreciate constructive feedback from reviewers if it reads well or it is unclear and confusing. * Currently we miss upgrade tests because we do not have JDK11 upgrade tests yet * The simulator still does not support JDK17 so I added only JDK11 simulator tests * Current table of all test failures with respective ticket numbers will be posted on CASSANDRA-16895 after this one gets committed. * I also plan to send email update to @dev when this gets committed. It will inform people that the new configuration is available. Patch - [https://github.com/apache/cassandra/commit/88dc2a6c7690472d78b428384793e383f37499dc] CI run [#2318|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18247-trunk-v2]: started new run of j11_cqlsh_dtests_py311 [here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2318/workflows/7eb1fe27-71d0-46d9-9feb-4cdb65e0153e/jobs/19642] - there was a git clone issue in the previous run; this one completed all good Other JDK11 tests completed successfully JDK17 seems good that it ran all tests we wanted with the resources we wanted and the right JDK. I will make a write up of the failures as per my earlier suggestion. was: *Summary:* * Added separate CircleCI configuration files for JDK11+17 plus created a respective generate_11_and_17.sh script. The differentiator for all new files is they all end up with "_11_and_17" suffix as part of their names. The new script operates the new config files in the way generate.sh operates on the old JDK8+11 configuration files. Why I chose to do it that way? - I believe this will make it easy when the time to switch to 11+17 come. * Updated the readme. I would appreciate constructive feedback from reviewers if it reads well or it is unclear and confusing. * Currently we miss upgrade tests because we do not have JDK11 upgrade tests yet * The simulator still does not support JDK17 so I added only JDK11 simulator tests * Current table of all test failures with respective ticket numbers will be opened on CASSANDRA-16895 after this one gets committed. * I also plan to send email update to @dev when this gets committed. It will inform people that the new configuration is available. Patch - [https://github.com/apache/cassandra/commit/88dc2a6c7690472d78b428384793e383f37499dc] CI run [#2318|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18247-trunk-v2]: started new run of j11_cqlsh_dtests_py311 [here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2318/workflows/7eb1fe27-71d0-46d9-9feb-4cdb65e0153e/jobs/19642] - there was a git clone issue in the previous run; this one completed all good Other JDK11 tests completed successfully JDK17 seems good that it ran all tests we wanted with the resources we wanted and the right JDK. I will make a write up of the failures as per my earlier suggestion. > Add CircleCI config files for J11+J17 > ------------------------------------- > > Key: CASSANDRA-18247 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18247 > Project: Cassandra > Issue Type: Task > Components: CI > Reporter: Ekaterina Dimitrova > Assignee: Ekaterina Dimitrova > Priority: Normal > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > Based on the direction of [this > discussion|https://lists.apache.org/thread/hchv59c1sntgb74clynj0zfd8jvwdmgy], > I would like to propose CircleCI config files which can be used to test > current trunk with JDK 17 (after I blindly remove the scripted UDFs in > another ticket, to be opened soon) -- 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