FrankChen021 opened a new issue, #20810: URL: https://github.com/apache/druid/issues/20810
_This issue was generated automatically by Claude Code (Anthropic's AI coding agent) running a scheduled CI-triage routine on behalf of @FrankChen021. Analysis and suggested fixes are AI-produced; please verify before acting on them._ **Status:** Resolved by #20608 **Subject:** `EmbeddedSecureJdbcDriverTest` `setUp` (jdbc-driver, `unit tests (25, E*,G*,F*)`) **Failures:** 1 · **First seen:** 2026-10-31 · **Last seen:** 2026-10-31 ### Root cause All 18 tests failed in `EmbeddedJdbcDriverTest.setUp` → `runIndexTask`: each index task succeeded, but `waitForAllSegmentsToBeAvailable` timed out after 10 s because the Broker never saw the new segments, for the whole ~3-minute class run. A Historical that stops loading for minutes matches the lost wakeup in `SegmentLoadDropHandler.processBatch()` fixed by #20608: a missed callback leaves the load batch waiting until the 5-minute `loadqueuepeon` host timeout. The failing commit (`5abae39110`, #20781, an Overlord config fix) was merged 4 minutes before #20608. This is a different failure mode from #20551 (surefire fork exits with code 1). ### Suggested fix No change needed if #20608 holds; this issue closes after 7 days without a recurrence. If it recurs, raise the wait in `runIndexTask` and check the Historical log in the run's test-report artifact for a stalled load batch. ### Occurrences Failed push-triggered master jobs only. The daily triage routine adds one row per new failed job. | Date | Commit | Job | Failure log | Detail | Reported in | |---|---|---|---|---|---| | 2026-10-31 | 5abae39110 (#20781) | `unit tests / unit tests(main) (25, E*,G*,F*) / test-jdk25-[E*,G*,F*]` | [job 124378508070](https://github.com/apache/druid/actions/runs/41148306776/job/124378508070) | 18/18 tests: `setUp` timed out after 10 s in `waitForAllSegmentsToBeAvailable`; no retry | | -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
