FrankChen021 opened a new issue, #20601: URL: https://github.com/apache/druid/issues/20601
_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:** Fix PR #20313 open **Subject:** `EmbeddedDartReportApiTest` (embedded-tests, `unit tests / unit tests(main) (25, E*,G*,F*)`) **Failures:** 1 · **First seen:** 2026-10-14 · **Last seen:** 2026-10-14 ### Root cause The class started at 21:19 UTC and never reported a result; the job step was killed at its 60-minute timeout about 43 minutes later. Every test method has `@Timeout(60)`, so the hang is outside test methods: most likely cluster shutdown in `@AfterAll` blocked on a Dart controller that keeps retrying `/workOrder` after `test_getQueryReport_forRunningAndCanceledQuery` cancels a query (the scenario #20313 describes), or the `@BeforeAll` ingestion wait. The commit (#20541) only changes v10 segment and projection capability handling, not Dart, and the same job passed on the next master commits. ### Suggested fix Land #20313, which cancels active `/workOrder` futures when a worker is stopped and touches this test. Also bound lifecycle methods (for example `junit.jupiter.execution.timeout.lifecycle.method.default` in embedded-tests) so a hang fails the class with a thread dump instead of consuming the whole job. ### 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-14 | 7004ad7838 (#20541) | `unit tests / unit tests(main) (25, E*,G*,F*) / test-jdk25-[E*,G*,F*]` | [job 115461843943](https://github.com/apache/druid/actions/runs/38445258244/job/115461843943) | class hung after `Running EmbeddedDartReportApiTest`; step killed at 60-minute timeout, no surefire result | | -- 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]
