[ https://issues.apache.org/jira/browse/CASSANDRA-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729866#comment-17729866 ]
Ekaterina Dimitrova edited comment on CASSANDRA-18285 at 6/6/23 11:58 PM: -------------------------------------------------------------------------- I added for trunk JDK11 upgrade tests, removing JDK 8 upgrade tests - both Java and Python. Unfortunately, 16 new Python upgrade tests are failing in CircleCI. Those are skipped in Jenkins, similar to CASSANDRA-18499. Unfortunately, I cannot load the artifacts page in CircleCI or reproduce the failures locally. Even if I add --force-resource-intensive-tests as suggested in CASSANDRA-18499. What is weird is I found those running with JDK 8 in CircleCI, like for example here test_parallel_upgrade - it seems it was upgrading from 4.1 with JDK8 - [https://app.circleci.com/pipelines/github/bereng/cassandra/970/workflows/2e949ede-cae5-4ab8-a118-43ec6d722b0d/jobs/18811/artifacts] [~mck] do you mind to review if I am doing something stupid and there is some additional check or anything to be added? After we confirm I didn't break anything myself here, I will also go ahead and add JDK11 upgrade tests for 4.0 and 4.1 (without removing JDK 8 upgrade tests which will run all paths where that one is needed - upgrades from 3.0 and 3.11) [CI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2362/workflows/fcbacaf2-eacc-491b-a920-07316a9efc73/jobs/24111/tests], [Patch|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:cassandra:18285-trunk-3?expand=1] was (Author: e.dimitrova): I added for trunk JDK11 upgrade tests, removing JDK 8 upgrade tests - both Java and Python. Unfortunately, 16 new Python upgrade tests are failing in CircleCI. Those are skipped in Jenkins, similar to CASSANDRA-18499. Unfortunately, I cannot load the artifacts page in CircleCI and reproduce the failures locally. Even if I add --force-resource-intensive-tests as suggested in CASSANDRA-18499. What is weird is I found those running with JDK 8 in CircleCI, like for example here test_parallel_upgrade - it seems it was upgrading from 4.1 with JDK8 - [https://app.circleci.com/pipelines/github/bereng/cassandra/970/workflows/2e949ede-cae5-4ab8-a118-43ec6d722b0d/jobs/18811/artifacts] [~mck] do you mind to review if I am doing something stupid and there is some additional check or anything to be added? After we confirm I didn't break anything myself here, I will also go ahead and add JDK11 upgrade tests for 4.0 and 4.1 (without removing JDK 8 upgrade tests which will run all paths where that one is needed - upgrades from 3.0 and 3.11) [CI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2362/workflows/fcbacaf2-eacc-491b-a920-07316a9efc73/jobs/24111/tests], [Patch|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:cassandra:18285-trunk-3?expand=1] > Add JDK 11 upgrade tests for 4.0+ in CircleCI > --------------------------------------------- > > Key: CASSANDRA-18285 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18285 > Project: Cassandra > Issue Type: Task > Components: CI > Reporter: Ekaterina Dimitrova > Assignee: Ekaterina Dimitrova > Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.x > > > Currently we test upgrades with Java 8, in preparation to drop it we need > first to ensurer we test with 11. This has to be added not only in trunk,, > but also 4.1 > I believe [~mck] has this ready to push in Jenkins at some point so this > ticket should accommodate the addition of those upgrade tests in CircleCI for > 4.1 and trunk. -- 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