[
https://issues.apache.org/jira/browse/CASSANDRA-15977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214813#comment-17214813
] Andres de la Peña commented on CASSANDRA-15977: ----------------------------------------------- Here are the CI results: 3.11 https://app.circleci.com/pipelines/github/adelapena/cassandra/116/workflows/4007a648-0a65-45a9-bcf6-4ef83017fbba https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-test/78/ https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-jvm-dtest/284/ https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-jvm-dtest-upgrade/76/ https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-dtest/114/ trunk https://app.circleci.com/pipelines/github/adelapena/cassandra/117/workflows/7efe9b9a-e2c6-40d4-a183-86ddd9e599f3 https://app.circleci.com/pipelines/github/adelapena/cassandra/117/workflows/18fe4de3-faaf-4bf9-a74c-f4fe04bf844f https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-test/79/ https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-jvm-dtest/285/ https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-jvm-dtest-upgrade/77/ [https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-dtest/115/] I'm seeing some timeout errors in {{ReadRepairQueryTypesTest}} (like [this one|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-jvm-dtest/285/testReport/junit/org.apache.cassandra.distributed.test/ReadRepairQueryTypesTest/testPointQueryOnWideTable_13__strategy_BLOCKING_coordinator_2_flush_false_paging_true_/] or [this other one|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch-jvm-dtest/282/testReport/junit/org.apache.cassandra.distributed.test/ReadRepairQueryTypesTest/testRangeQueryWithFilterOnSelectedColumnOnSkinnyTable_14__strategy_BLOCKING_coordinator_2_flush_true_paging_false_/]) that I can't reproduce locally. Not sure whether they might be caused by the CI environment or there's a real problem. Increasing the request timeout doesn't help, so we could try to not so aggressively reuse the cluster. Right now 224 tests use the same cluster, working with a cluster per test like most dtests do might improve this, although that would make the test significantly slower. CC [~maedhroz] > 4.0 quality testing: Read Repair > -------------------------------- > > Key: CASSANDRA-15977 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15977 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/unit > Reporter: Andres de la Peña > Assignee: Andres de la Peña > Priority: Normal > Fix For: 4.0-beta > > Time Spent: 13h 20m > Remaining Estimate: 0h > > This is a subtask of CASSANDRA-15579 focusing on read repair. > [This > document|https://docs.google.com/document/d/1-gldHcdLSMRbDhhI8ahs_tPeAZsjurjXr38xABVjWHE/edit?usp=sharing] > lists and describes the existing functional tests for read repair, so we can > have a broad view of what is currently covered. We can comment on this > document and add ideas for new cases/tests, so it can gradually evolve to a > more or less detailed test plan. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
