Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-18258

Add test conf for JDK17

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 5.0-alpha1, 5.0
    • Local/Config
    • None
    • Operability
    • Normal
    • All
    • None
    • Hide

       

      Patch CI 8+11 CI 11+17
      trunk CI CI

      Here it is preliminary config to enable start Cassandra and run at least Unit and JVM tests(the build.xml GC config should be changed in CASSANDRA-18263). I added some CircleCI tests so I can show at least the unit tests that they pickup the right things. Final agreement on what we want for CircleCI precisely will be made in CASSANDRA-18247 and I guess it might need revisit based on CASSANDRA-18133.
      I added IntelliJ IDEA target too but I am again in a loop with my IDE today. Now it sends me a message it cannot save my settings all the time...
      I will have to figure that out over the weekend.
      Please ignore the CircleCI files for now.
      Also, we had with Michael Semb Wever a conversation to add some exports for fqltool and auditlogviewer, I opted to add them in jvm17-clients.options (even if the other tools do not need them) as while they will be needed also with Java 11 after we upgrade Chronicle Queue, they cannot be used with Java 8 now.
      There are still some tests running but so far it seems we see JDK17 around 20 unit tests failing which we already know about - pending the ECJ upgrade, etc

       

      PS the jvm args in build.xml can be split in a more beautiful way but considering this is temporarily until we drop JDK8 which will simplify and get back us to where we were, I opt out of spending too much time on those.

      Show
        Patch CI 8+11 CI 11+17 trunk CI CI Here it is preliminary config to enable start Cassandra and run at least Unit and JVM tests(the build.xml GC config should be changed in CASSANDRA-18263 ). I added some CircleCI tests so I can show at least the unit tests that they pickup the right things. Final agreement on what we want for CircleCI precisely will be made in CASSANDRA-18247 and I guess it might need revisit based on CASSANDRA-18133 . I added IntelliJ IDEA target too but I am again in a loop with my IDE today. Now it sends me a message it cannot save my settings all the time... I will have to figure that out over the weekend. Please ignore the CircleCI files for now. Also, we had with Michael Semb Wever a conversation to add some exports for fqltool and auditlogviewer, I opted to add them in jvm17-clients.options (even if the other tools do not need them) as while they will be needed also with Java 11 after we upgrade Chronicle Queue, they cannot be used with Java 8 now. There are still some tests running but so far it seems we see JDK17 around 20 unit tests failing which we already know about - pending the ECJ upgrade, etc   PS the jvm args in build.xml can be split in a more beautiful way but considering this is temporarily until we drop JDK8 which will simplify and get back us to where we were, I opt out of spending too much time on those.

    Description

      Post CASSANDRA-18252 and CASSANDRA-18179 we will be able to compile current trunk with JDK17 but in order to start Cassandra and test it we will need also our conf files updated with some preliminary conf for test purposes.

      This ticket will be used to add those to current trunk

      Attachments

        Activity

          People

            e.dimitrova Ekaterina Dimitrova
            e.dimitrova Ekaterina Dimitrova
            Ekaterina Dimitrova
            Michael Semb Wever
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: