DanielLeens commented on PR #11602:
URL: https://github.com/apache/seatunnel/pull/11602#issuecomment-5713043150

   Thanks for following up. Confirmed: on run `35145655123` against head 
`c30188e0fb70`, both `engine-v2-it` legs (JDK 8 and JDK 11) are green -- that 
closes out the one non-blocking follow-up from my 2026-09-17 review (I'd asked 
to see that leg confirmed before treating this as merge-ready).
   
   On the remaining red jobs, I don't think any of them need a closer 
comparison: this PR's diff touches only `seatunnel-engine-common`, 
`seatunnel-engine-server`, the engine E2E test, `config/seatunnel.yaml`, and 
the two `incompatible-changes.md` docs (confirmed via `gh pr diff 
--name-only`). It does not touch any connector module, so `all-connectors-it` 
shards 2/6/7 and `doris-connector-it` (JDK 8) are structurally outside anything 
this diff could cause. `paimon-connector-it` failing on both JDK legs matches 
the previously-confirmed, pre-existing Paimon classloader-hang issue that's 
unrelated to Zeta-engine PRs and has hit other unrelated branches too -- no 
need to reproduce that one against `dev` yourself, it's a known issue on the 
connector side.
   
   One more data point since you're tracking sync state: the branch is now 
`ahead_by: 19, behind_by: 44` against `dev` (still `mergeable: MERGEABLE`, no 
conflict, just diverged further since my last check). Not a blocker, but a 
rebase before merge would keep the CI evidence current given how far behind 
it's gotten.
   
   From the engine-side source review I don't have anything further open. I'll 
leave the formal merge call and any re-approval to the next full pass once 
there's a reason to trigger one (a new commit, or a maintainer request) -- for 
now this looks ready modulo the housekeeping rebase above.


-- 
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]

Reply via email to