ammachado opened a new pull request, #30214:
URL: https://github.com/apache/camel/pull/30214

   JIRA: https://issues.apache.org/jira/browse/CAMEL-27007
   
   Test-only changes that cut idle waiting in camel-core tests (the surefire 
run of camel-core is on the critical path of the CI build).
   
   - `ThrottlingExceptionRoutePolicyOpenViaConfigTest` (31-61 s to 0.9 s): each 
phase now resets the mock and sets its expectation BEFORE sending. 
`expectedMessageCount(n)` creates a new latch that ignores messages already 
received, so setting it afterwards waited the full timeout.
   - `TimerFirstFireAfterRouteRestartTest` (10.3 s to 0.19 s): same latch trap, 
replaced by a direct `getReceivedCounter()` assertion.
   - `DataSetConsumerTest` (10 s to 0.3 s): `isUseAdviceWith()` so the context 
starts after the expectations are set.
   - `MulticastParallelStreamingTest`: 5 sequential messages instead of 10 
(concurrent sends starve the multicast thread pool and change the order).
   - `support.task` tests (`ForegroundTaskTest`, `ForegroundTimeTaskTest`, 
`BackgroundIterationTimeTaskTest`): intervals, delays and durations scaled by 
5; they only count iterations. The slow predicate sleep is now a 
`slowPredicateMillis()` hook in `TaskTestSupport` (default 2000), so 
`BackgroundTaskTest`, which asserts elapsed seconds, is unchanged.
   
   Verified: full camel-core run, 9460 tests, 0 failures, and the touched 
classes run repeatedly without flakiness. The total gain of the full module run 
is within run-to-run noise (about 2:15 to 2:33 vs 2:58 baseline).
   
   _Claude Code on behalf of ammachado_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to