You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2026/07/13 07:03:00 UTC

[jira] [Updated] (CAMEL-24037) Fix flaky camel-core tests: TwoSchedulerTest, DistributedTimeoutTest, ThrottlingExceptionRoutePolicyOpenViaConfigTest

     [ https://issues.apache.org/jira/browse/CAMEL-24037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated CAMEL-24037:
------------------------------------
    Fix Version/s: 4.22.0

> Fix flaky camel-core tests: TwoSchedulerTest, DistributedTimeoutTest, ThrottlingExceptionRoutePolicyOpenViaConfigTest
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-24037
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24037
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>            Priority: Major
>              Labels: test-flaky
>             Fix For: 4.22.0
>
>
> Several camel-core tests are flaky in CI due to timing issues:
> - TwoSchedulerTest: uses assertMockEndpointsSatisfied() without timeout, and assertSame for String comparison (should use assertEquals)
> - DistributedTimeoutTest: wraps MockEndpoint assertions with Awaitility (anti-pattern per project guidelines), needs direct timed assertions
> - ThrottlingExceptionRoutePolicyOpenViaConfigTest: uses assertMockEndpointsSatisfied() without timeout
> Fix by using MockEndpoint.assertIsSatisfied(context, 30, TimeUnit.SECONDS) timed assertions and correcting the String comparison.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)