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

   ## Summary
   
   _Claude Code on behalf of gnodet_
   
   Fix 4 flaky tests in `camel-quartz` identified by [Develocity 
analytics](https://develocity.apache.org):
   
   | Test | Flaky rate | Root cause | Fix |
   |---|---|---|---|
   | `QuartzAddRoutesAfterCamelContextStartedTest` | 3.2% (48/1483) | 
`repeatInterval=100ms` too tight for loaded CI | Increased to 500ms, added 
timed assertion |
   | `QuartzCronRouteWithStartDateEndDateTest` | 2.5% (37/1483) | Narrow 2s 
trigger window with only 3s setup headroom | Widened to 4s window with 5s 
headroom, proper timed assertion |
   | `QuartzAddDynamicRouteTest` | 1.7% (25/1483) | `repeatInterval=2ms` — 
absurdly tight for any scheduler | Increased to 200ms, added timed assertion |
   | `CronScheduledRoutePolicyTest$CronTest5` | 0.3% (5/1483) | `await(5000, 
TimeUnit.SECONDS)` — 83 minutes! (typo) | Fixed to `await(30, 
TimeUnit.SECONDS)`, assert result |
   
   ### Details
   
   **QuartzAddRoutesAfterCamelContextStartedTest**: The Quartz scheduler thread 
pool can be starved on loaded CI machines. A 100ms repeat interval with 
`repeatCount=1` means two firings must happen within ~200ms — too tight. 
Increased to 500ms.
   
   **QuartzCronRouteWithStartDateEndDateTest**: The cron trigger starts 3 
seconds in the future and fires for only 2 seconds. On loaded CI, Quartz 
scheduler initialization can take >1 second, eating into the headroom. 
Increased start offset to 5s and window to 4s. Also replaced the redundant 
`mock.await()` + `assertIsSatisfied()` chain with a single timed 
`assertIsSatisfied`.
   
   **QuartzAddDynamicRouteTest**: A 2ms repeat interval is far below Quartz's 
scheduling granularity. Both firings can happen before the mock is ready, or 
the scheduler may miss them entirely. Increased to 200ms.
   
   **CronScheduledRoutePolicyTest$CronTest5**: `startedLatch.await(5000, 
TimeUnit.SECONDS)` is clearly a typo — 5000 seconds = 83 minutes. Fixed to 30 
seconds with proper assertion of the latch result for fail-fast behavior.
   
   ## Test plan
   
   - [x] All 4 fixed tests pass locally (5 consecutive runs)
   - [ ] CI green on this PR
   
   🤖 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