DanielLeens commented on PR #11307: URL: https://github.com/apache/seatunnel/pull/11307#issuecomment-5322431161
Thanks @SEZ9 — quick status update so we don't duplicate a cycle here. The sync you're asking for already happened at the current head (`a87908b9`): @goutamadwant merged latest `dev` on 2026-08-15, right before my most recent full re-review of this PR. I independently diffed `b2cd470fc..a87908b9` and confirmed the only change was that no-op `dev` merge — none of this PR's owned files (Spark starter/translation/E2E/docs) were touched by it. That CI run has since completed (it was still queued when I reviewed): https://github.com/goutamadwant/seatunnel/actions/runs/31854377024. The only failing job is `all-connectors-it-3`, and the only failing test in it is `DruidIT.testDruidSink`, with an `org.awaitility.core.ConditionTimeoutException` at `DruidIT.java:105` — a Druid E2E container timeout, unrelated to anything in this PR's Spark diff. That said, per the current compare status the branch is now behind the latest `dev` by ~11 commits (dev kept moving after the 08-15 sync), so @goutamadwant it's still worth one more sync + rerun to pick up any recent CI-side fixes and get a clean signal. Just flagging expectations: a sync alone probably won't "fix" this particular Druid flake, so if it recurs afterwards it's most likely an environment-side flake rather than something in the diff — a job-level rerun of just `all-connectors-it-3` should be enough at that point rather than a broader investigation. -- 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]
