[
https://issues.apache.org/jira/browse/CAMEL-24037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095797#comment-18095797
]
Guillaume Nodet commented on CAMEL-24037:
-----------------------------------------
Fixed via merged PR: https://github.com/apache/camel/pull/24037
> 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)
