gnodet opened a new pull request, #23178: URL: https://github.com/apache/camel/pull/23178
## Summary Tighten 8 tests in `camel-core` that failed during full-suite parallel execution under heavy CI load. These tests are stable in isolation but flaky when 2700+ tests run concurrently. ## Changes by test | # | Test | Root Cause | Fix | |---|---|---|---| | 1 | `SedaBlockWhenFullTest#testAsyncSedaBlockingWhenFull` | `resultWaitTime=390ms` and `assertMockEndpointsSatisfied(2s)` too tight for async seda under load | Increase `resultWaitTime` to `DELAY_LONG * 10`; assertion timeout 2→5s | | 2 | `AggregateExpressionTimeoutFallbackTest` | `completionTimeout(2000)` barely enough under load | Increase to 3000ms | | 3 | `AggregateCompleteAllOnStopWithIntervalTest` | `mock.assertIsSatisfied()` called immediately after `context.stop()` — shutdown is async | Wrap with `await().atMost(5s).untilAsserted()` | | 4 | `AsyncEndpointRedeliveryErrorHandlerNonBlockedDelay2Test` | Static `LongAdder attempt` never reset between runs; also `mock:result` used for both `before` and `result` variables (copy-paste bug) | Add `@BeforeEach` to reset counter; fix mock variable to use `mock:before` | | 5 | `AggregateTimeoutOnlyTest` | `setResultMinimumWaitTime(900)` with 1s completion timeout — under load timer fires late | Reduce minimum wait to 500ms | | 6 | `AggregateDiscardOnFailureTest` | `completionTimeout(2000)` could fire a stale aggregation under load | Increase to 3000ms | | 7 | `AggregateForceCompletionOnStopParallelTest` | `parallelProcessing().delay(100)` means completion processor runs in background thread; immediate assertion after `stopRoute()` races | Override `testForceCompletionTrue` and `testStopRouteForceCompletionTrue` with Awaitility | | 8 | `ContextScopedOnExceptionLoadBalancerStopRouteTest#testErrorOk` | Seda error route processing slow under load | Add explicit `setResultWaitTime(5000)` on `mock:error` | _Claude Code on behalf of Guillaume Nodet_ -- 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]
