[ https://issues.apache.org/jira/browse/CASSANDRA-18707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771532#comment-17771532 ]
Ekaterina Dimitrova edited comment on CASSANDRA-18707 at 10/3/23 3:49 PM: -------------------------------------------------------------------------- {quote}I was trying to spare CI cycles so I didn't run all jdks, but I added them now for completion. {quote} I think I may be looking in the wrong place, so I am posting the links I used to verify CI here: [4.0 |https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18707-4.0] hit CASSANDRA-18158, but I do not see J11 run. [4.1 |https://app.circleci.com/pipelines/github/bereng/cassandra/1089/workflows/6cbb8ed4-221a-4ae4-88b6-bd08579c144f/jobs/31124] - I do not see J11 runs [5.0 |https://app.circleci.com/pipelines/github/bereng/cassandra/1090/workflows/8bcb9c45-7a72-4ae2-a62b-970e9f66a1d3/jobs/31125] - I do not see J17 runs [trunk |https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18707-trunk] - I do not see J17 runs I also just realized (absolutely my fault, so leave it for a follow-up ticket, please, apologize) that the timeout is not configurable with -D or so - being in CASSANDRA_RELEVANT_PROPERTIES, for example. {quote}The repeated runs I did didn't repro the issue. {quote} Yes, but the raised timeout can have a side effect. I spun the test locally on 5.0 100 times with your patch applied, and there were no issues, so I suggest we skip that in CI. +1 on green CI (the missing JDK runs) was (Author: e.dimitrova): {quote}I was trying to spare CI cycles so I didn't run all jdks, but I added them now for completion. {quote} I think I may be looking in the wrong place, so I am posting the links I used to verify CI here: [4.0 |https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18707-4.0] hit CASSANDRA-18158, but I do not see J11 run. [4.1 |https://app.circleci.com/pipelines/github/bereng/cassandra/1089/workflows/6cbb8ed4-221a-4ae4-88b6-bd08579c144f/jobs/31124] - I do not see J11 runs [5.0 |https://app.circleci.com/pipelines/github/bereng/cassandra/1090/workflows/8bcb9c45-7a72-4ae2-a62b-970e9f66a1d3/jobs/31125] - I do not see J17 runs [trunk |https://app.circleci.com/pipelines/github/bereng/cassandra?branch=CASSANDRA-18707-trunk] - I do not see J17 runs I also just realized (absolutely my fault, so leave it for a follow-up ticket, please, apologize) that the timeout is not configurable with -D or so - being in CASSANDRA_RELEVANT_PROPERTIES, for example. {quote}The repeated runs I did didn't repro the issue. {quote} Yes, but the raised timeout can have a side effect. I spun it locally on 5.0 100 times, and there were no issues, so I suggest we skip that in CI. +1 on green CI (the missing JDK runs) > Test failure: > junit.framework.TestSuite.org.apache.cassandra.distributed.test.CASMultiDCTest-.jdk11 > > ---------------------------------------------------------------------------------------------------- > > Key: CASSANDRA-18707 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18707 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/java > Reporter: Ekaterina Dimitrova > Assignee: Berenguer Blasi > Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x > > Attachments: TESTS-TestSuites.xml.xz > > > Seen here: > [https://ci-cassandra.apache.org/job/Cassandra-trunk/1650/testReport/junit.framework/TestSuite/org_apache_cassandra_distributed_test_CASMultiDCTest__jdk11/] > h3. > {code:java} > Error Message > Schema agreement not reached. Schema versions of the instances: > [ef1c8e05-a06d-388d-a46d-53cc22a94762, 6c386108-1805-3985-b48e-8016012a0207, > 6c386108-1805-3985-b48e-8016012a0207, ef1c8e05-a06d-388d-a46d-53cc22a94762] > Stacktrace > java.lang.IllegalStateException: Schema agreement not reached. Schema > versions of the instances: [ef1c8e05-a06d-388d-a46d-53cc22a94762, > 6c386108-1805-3985-b48e-8016012a0207, 6c386108-1805-3985-b48e-8016012a0207, > ef1c8e05-a06d-388d-a46d-53cc22a94762] at > org.apache.cassandra.distributed.impl.AbstractCluster$ChangeMonitor.waitForCompletion(AbstractCluster.java:907) > at > org.apache.cassandra.distributed.impl.AbstractCluster.lambda$schemaChange$8(AbstractCluster.java:836) > at org.apache.cassandra.concurrent.FutureTask$1.call(FutureTask.java:96) at > org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61) at > org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71) at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at > io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) > at java.base/java.lang.Thread.run(Thread.java:829) > {code} > -- 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