DanielLeens commented on PR #13005: URL: https://github.com/apache/seatunnel/pull/13005#issuecomment-6557307361
Thanks again. The CI fact cited in my last full review has changed: the previously in-progress Build is now TIMED_OUT on the unchanged head. The concrete unfinished execution is [RocketMQ JDK 11 job 124246594927](https://github.com/goutamadwant/seatunnel/actions/runs/41019844398/job/124246594927). Its GitHub annotation explicitly says “The job has exceeded the maximum execution time of 2h0m0s”; the fork run and this job are cancelled. This is not evidence of a failed configuration-variable assertion. I checked the latest dev history/content for backend/build_main and the RocketMQ E2E path against this head: no corresponding workflow or RocketMQ change supplies an established timeout cure. A sync alone is therefore not the demonstrated fix. The lowest-cost next step is to check whether a newer Build is already active, then retry only that RocketMQ job if appropriate. If it reaches the same limit again, collect the in-flight test/thread diagnostics rather than changing unrelated CLI/configuration code or replaying the whole workflow. My preceding full review left no production source blocker; its two fixture/checklist recommendations remain non-blocking. The remaining technical gate is a successful exact-head execution of that cancelled lane. I could retrieve the timeout annotation, but full-log downloads failed with stream EOF/CANCEL errors; I am not inventing a specific hung test or the underlying cause of its duration. Checked 2026-11-01T11:26:42.133859+00:00; unchanged head `32e748f711ea6c51b59d49a8d7f6f9d6e5beaaf7`. Current checks: [Build](https://github.com/apache/seatunnel/runs/123950878132)=TIMED_OUT. Base `dev`, compare `diverged`, ahead 4 / behind 9; merge `UNKNOWN` / `REVIEW_REQUIRED`. Drift is recorded independently; it does not itself request synchronization. Daniel has READ permission. This is a CI/merge-gate clarification, not another full source review, effective approval or dismissal. -- 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]
