CAMEL-24787 - reduce flakiness of Cassandra Integration tests - #26582
Merged
Merged
Conversation
there is regularly this stack: ``` com.datastax.oss.driver.api.core.DriverTimeoutException: Query timed out after PT5S at com.datastax.oss.driver.api.core.DriverTimeoutException.copy(DriverTimeoutException.java:36) at com.datastax.oss.driver.internal.core.util.concurrent.CompletableFutures.getUninterruptibly(CompletableFutures.java:154) at com.datastax.oss.driver.internal.core.cql.CqlRequestSyncProcessor.process(CqlRequestSyncProcessor.java:55) at com.datastax.oss.driver.internal.core.cql.CqlRequestSyncProcessor.process(CqlRequestSyncProcessor.java:32) at com.datastax.oss.driver.internal.core.session.DefaultSession.execute(DefaultSession.java:234) at com.datastax.oss.driver.api.core.cql.SyncCqlSession.execute(SyncCqlSession.java:56) at com.datastax.oss.driver.api.core.cql.SyncCqlSession.execute(SyncCqlSession.java:80) at org.apache.camel.component.cassandra.integration.BaseCassandra.executeCql(BaseCassandra.java:75) at org.apache.camel.component.cassandra.integration.BaseCassandra.executeScript(BaseCassandra.java:69) at org.apache.camel.component.cassandra.integration.BaseCassandra.executeScript(BaseCassandra.java:61) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at java.base/java.util.ArrayList.forEach(ArrayList.java:1596) at java.base/java.util.ArrayList.forEach(ArrayList.java:1596) ``` the test when passing is usually taking between 2 and 4 seconds so maybe a bit too close from the timeout of the request Signed-off-by: Aurélien Pupier <apupier@ibm.com>
oscerd
approved these changes
Sep 18, 2026
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
Contributor
|
🧪 CI tested the following changed modules:
🔬 Scalpel shadow comparison — Scalpel: 1 tested, 0 compile-only — current: 9 all testedMaveniverse Scalpel detected 1 affected modules (current approach: 9). Modules only in current approach (8)
Skip-tests mode would test 1 modules (1 direct + 0 downstream), skip tests for 0 (generated code, meta-modules) Modules Scalpel would test (1)
All tested modules (9 modules, 1m 39s total)Total reactor time: 1m 39s
Top 20 slowest modules:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
there is regularly this stack:
the test when passing is usually taking between 2 and 4 seconds so maybe a bit too close from the timeout of the request
Description
Target
mainbranch)Tracking
Apache Camel coding standards and style
mvn clean install -DskipTestslocally from root folder and I have committed all auto-generated changes.AI-assisted contributions
Co-authored-bytrailers) and the PR description identifies the AI tool used.