[
https://issues.apache.org/jira/browse/CAMEL-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-24063 started by Guillaume Nodet.
-----------------------------------------------
> Fix flaky tests: JMS, Seda, Disruptor, Scheduler, and Direct timing issues
> --------------------------------------------------------------------------
>
> Key: CAMEL-24063
> URL: https://issues.apache.org/jira/browse/CAMEL-24063
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, camel-disruptor, camel-jms
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Major
>
> Several tests across multiple modules exhibit flaky behavior on CI due to
> timing-related issues:
> *JMS tests:*
> - JmsAddAndRemoveRouteManagementIT (15 flakes/3 days, 9.0% flake rate): No
> route ID on initial consumer route preventing JMS readiness check. Fixed by
> adding routeId and waitForJmsConsumerRoutes.
> - JmsDurableTopicIT (6 flakes/3 days, 3.6% flake rate): Bare
> assertIsSatisfied with default 10s timeout too short for topic subscription
> on slow CI. Fixed by using timed assertion.
> *Seda/Disruptor tests:*
> - SedaBlockWhenFullTest (7 flakes/3 days, 8.4% flake rate): @Timeout(20)
> conflicts with 30s mock assertion timeout - JUnit kills the test before mock
> can complete. Fixed by increasing to @Timeout(60).
> - DisruptorBlockWhenFullTest (4 flakes/3 days, 4.8% flake rate): Bare
> assertIsSatisfied with default 10s timeout too short for 28 messages at 100ms
> delay. Fixed by using timed assertion.
> *Scheduler test:*
> - SchedulerNoPolledMessagesTest (8 flakes/3 days, 9.6% flake rate):
> Inter-message arrival timing windows too tight for CI with GC pauses. Fixed
> by widening timing windows.
> *Direct test:*
> - DirectProducerBlockingTest (3 flakes/3 days, 3.6% flake rate): Tight lower
> bound (490ms) for 500ms timeout fails with thread scheduling jitter. Fixed by
> relaxing to 400ms and using timed mock assertion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
