DanielLeens commented on PR #11029: URL: https://github.com/apache/seatunnel/pull/11029#issuecomment-5200417939
Quick sync-status note on top of my earlier review of this exact head. This branch is currently behind `dev` again (diverged, `behind_by=6`, `ahead_by=7`), and the `Build` check is still red on the same run I already analyzed: a single failing lane, `Run / unit-test (11, windows-latest)`, which fails about 8.5 minutes into a ~60-minute step, well before the reactor reaches the `connector-cdc` modules this PR touches. All 69 other jobs (both JDK 8 and 11, including `all-connectors-it-1..8`, which exercise the Postgres-CDC/OpenGauss-CDC E2E suites end-to-end) are green, and the same lane passed the same day on a sibling branch built off the same `dev`. So I still do not believe this failure is caused by this PR's diff. Since then, `dev` has also picked up a few CI-stability fixes (including Hazelcast test port isolation and hosted-connector IT stabilization), so the lowest-cost next step now is to sync this branch onto the latest `dev` and rerun CI, rather than just re-running the same lane in isolation. To be clear, this is on top of the one real blocker from my last review, which still needs to be addressed regardless of CI: adding the small regression test for the `require-replica-identity-full` dialect wiring and disclosing the enforcement restoration in the PR description. If the `Build` check still fails after the sync, please share the log and I'll dig into that specific lane. -- 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]
