davidzollo commented on PR #11856: URL: https://github.com/apache/seatunnel/pull/11856#issuecomment-5555528513
CI is green on `e6e243744e3` — the fork `Build` run (33966670706) finished with all 83 non-skipped jobs passing and the `Build` check on this PR reports success. For the record, what it took after merging `dev` (`e6e243744e3` is a pure merge commit; the three-dot diff is unchanged): - `all-connectors-it-7` (the `PostgresCDCIT` committed-offset timeout, #11847) passed on both JDKs once the branch had #11644's larger restore budget. - `jdbc-connectors-it-part-1 (8)` / `part-4 (8)` failed once on runner networking (TLS handshake during the Maven wrapper download; `Connection reset` from Maven Central resolving `testcontainers:postgresql`) and passed on rerun. - `rocketmq-connector-it (8)` failed twice with `MQClientException: The broker[broker-a] not exist` / `No topic route info` across all container variants and passed on the third attempt. That signature is byte-identical to `dev`'s own run 33970546560 (`rocketmq-connector-it (11)`, 2026-09-05), and `RocketMqIT`/`RocketMqContainer` were last changed by #12050, so it looks like a dev-level intermittent failure rather than anything in this diff — worth a separate look upstream. Review status is unchanged from the last full pass: no blocking items, only the optional Issue 5 hardening carried. @SEZ9 re-requesting your review — everything from your `CHANGES_REQUESTED` round and the later race finding is closed on this head. -- 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]
