ryanmeowy commented on PR #13147: URL: https://github.com/apache/seatunnel/pull/13147#issuecomment-6734742422
Thanks for the CI diagnosis — retrying was the right call. I re-ran the Build workflow on the unchanged head `3d7944f1d518e8065c1b295b42bbbae3596cddb8`. Attempt 2 completed successfully, so the two lanes that failed earlier no longer fail and need no separate attribution: the `engine-v2-it (17, ubuntu-latest)` failure was the Docker registry connection reset you identified, and `kafka-connector-it (17, ubuntu-latest)` did not reproduce on the retry. - Fork Build (attempt 2): https://github.com/ryanmeowy/seatunnel/actions/runs/42034523942 - Apache-side required `Build` on the same head: https://github.com/apache/seatunnel/runs/127824712049 — success, completed 2026-11-06T12:40:55Z There are no code changes since your review, so your source conclusion still applies. The branch is 38 commits behind `dev` but remains mergeable; I left it unsynced, since your note said branch age alone does not justify a sync. That leaves only the write-capable maintainer approval that you identified as the final gate. Could you re-confirm your technical conclusion on this head — and record it as an approval if you are comfortable doing so — so it is visible to a committer picking this up that both the source and CI gates are cleared? Thank you again for the careful review. -- 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]
