(camel) branch main updated: CAMEL-25220: camel-quartz - Fix flaky SpringQuartzConsumerTwoAppsClusteredRecoveryTest

[fmariani]

This is an automated email from the ASF dual-hosted git repository.

Croway pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 05ac29de8017 CAMEL-25220: camel-quartz - Fix flaky 
SpringQuartzConsumerTwoAppsClusteredRecoveryTest
05ac29de8017 is described below

commit 05ac29de8017fffc123d7f4f5bb019c636ab4df7
Author: Urmila Unni <urmila8...@gmail.com>
AuthorDate: Thu Oct 8 21:19:09 2026 +0530

    CAMEL-25220: camel-quartz - Fix flaky 
SpringQuartzConsumerTwoAppsClusteredRecoveryTest
    
    Allow 30s for the cluster recovery instead of Awaitility's 10s default.
    
    Co-authored-by: Claude <nore...@anthropic.com>
---
 .../quartz/SpringQuartzConsumerTwoAppsClusteredRecoveryTest.java   | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git 
a/components/camel-quartz/src/test/java/org/apache/camel/component/quartz/SpringQuartzConsumerTwoAppsClusteredRecoveryTest.java
 
b/components/camel-quartz/src/test/java/org/apache/camel/component/quartz/SpringQuartzConsumerTwoAppsClusteredRecoveryTest.java
index 9296f2d6a075..98c6464a03ef 100644
--- 
a/components/camel-quartz/src/test/java/org/apache/camel/component/quartz/SpringQuartzConsumerTwoAppsClusteredRecoveryTest.java
+++ 
b/components/camel-quartz/src/test/java/org/apache/camel/component/quartz/SpringQuartzConsumerTwoAppsClusteredRecoveryTest.java
@@ -16,6 +16,8 @@
  */
 package org.apache.camel.component.quartz;
 
+import java.util.concurrent.TimeUnit;
+
 import org.apache.camel.CamelContext;
 import org.apache.camel.Exchange;
 import org.apache.camel.Predicate;
@@ -62,8 +64,9 @@ public class SpringQuartzConsumerTwoAppsClusteredRecoveryTest 
{
         AbstractXmlApplicationContext app2 = 
newAppContext("SpringQuartzConsumerRecoveryClusteredAppTwo.xml");
         app2.start();
 
-        // wait long enough until the second app takes it over...
-        Awaitility.await().untilAsserted(() -> {
+        // Quartz only declares app-one failed after its check-in interval 
plus a fixed 7.5s grace period, so the
+        // recovery alone takes most of Awaitility's 10s default; allow enough 
time on a loaded CI machine
+        Awaitility.await().atMost(30, TimeUnit.SECONDS).untilAsserted(() -> {
             CamelContext camel2 = app2.getBean("camelContext2-" + 
getClass().getSimpleName(), CamelContext.class);
 
             MockEndpoint mock2 = camel2.getEndpoint("mock:result", 
MockEndpoint.class);