DanielLeens commented on PR #11721: URL: https://github.com/apache/seatunnel/pull/11721#issuecomment-5466073111
Quick CI diagnosis, since this hasn't been checked explicitly yet: `Build` on this head (`aea9854a1bb1`) shows `cancelled`. I followed the pointer to the real fork run (`SEPURI-SAI-KRISHNA/seatunnel` run `32746106023`) and checked every job in it rather than assuming the top-level status reflects a real failure. Every job that could plausibly touch this PR's diff passed, including `unit-test (8, ubuntu-latest)` — success. The only non-passing job in the whole run is `kudu-connector-it (11, ubuntu-latest)`, which ran for about 1.5 hours (`12:31:05` -> `14:01:35`) before being cancelled; `kudu-connector-it (8, ubuntu-latest)` on the same head passed cleanly a day earlier. This PR touches `MultiTableSinkWriter`'s hash-routing logic, its tests, and docs — nothing under `connector-kudu` — so a single stuck/timed-out Kudu IT job on one JDK variant isn't something this diff could have caused. Given every relevant job already passed and the one non-passing job looks like an isolated stuck/timeout on an unrelated connector module (this PR is also 24 commits behind `dev`, which doesn't help), the lowest-cost next step is a job-level rerun of just that job (`gh run rerun 32746106023 --job 97802143478` from the fork, or the Actions UI "Re-run failed jobs" button) rather than a full rebuild. This doesn't change my "Ready to merge" conclusion from the 08-24 review, which still stands with F1/F2 both closed out. -- 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]
