FrankChen021 opened a new issue, #20435:
URL: https://github.com/apache/druid/issues/20435

   _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:** Open: no fix PR
   **Subject:** `IngestionSmokeTest.test_streamLogs_ofCancelledTask`, seen via 
`ConsulDiscoveryPlainDockerTest` (embedded-tests, `docker-tests`)
   **Failures:** 1 · **First seen:** 2026-09-25 · **Last seen:** 2026-09-25
   
   ### Root cause
   
   Race: the test polls `TaskLogStreamer.streamTaskLog(taskId, 0)` only until 
the `Optional` is present. In the Docker setup, the peon's log is pushed after 
the process exits, so the stream can be present but empty, which fails 
`assertFalse(logs.isEmpty())` at `IngestionSmokeTest.java:398`. The TLS and 
MTLS variants passed in the same job.
   
   ### Suggested fix
   
   Move the read into the `waitForResult` supplier, and wait until the log 
contains `"Running task[%s] for [%d] millis"` instead of just 
`Optional::isPresent`.
   
   ### 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-09-25 | 53e814e87c (#20425) | `docker-tests` | [job 
108039867472](https://github.com/apache/druid/actions/runs/36125282875/job/108039867472)
 | streamed task log was empty; single attempt (no surefire retries) | #20428 |
   


-- 
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]

Reply via email to