zhangshenghang commented on PR #12163: URL: https://github.com/apache/seatunnel/pull/12163#issuecomment-5666666562
Thanks for re-verifying the restore-ack logic and for flagging the stale CI status — here's the trace of the fork Build failure (run 34791586655... rather, run 34791705815 for this head `01484485d`): Both failing job families are unrelated flakes, not the ack-chain change: 1. **`all-connectors-it-1/2/7` (8/11)** — the only failing test is `OpengaussCDCIT.testAddFieldWithRestore` (`ConditionTimeoutException: actual iterable was <null> ... within 1 minutes`, ~82s). The identical test fails with the identical signature in the independent fork runs of two sibling PRs going through dev-sync today: the Paimon-only PR #12301 (run 34795570724) and the Zeta-classloader-only PR #12271 (run 34792618245). Three PRs with zero file overlap (paimon sink / cdc-base ack / zeta TaskExecutionService) all failing the same opengauss restore test points at the shared opengauss container environment, not any of the three diffs. 2. **`engine-v2-it` (8/11)** — `SplitClusterFaultToleranceIT.testStreamJobCancelResolvesWhenWorkerCrashesBeforeCancelAck` errors after ~67s (worker-crash cancel race). Same signature in #12271's run, and this test already has a flake history in this repo (same cancel-race signature was hit and cleared by a rerun during #12161's CI round). Neither test touches `connector-cdc-base`'s restore-ack path that this PR changes, and this PR's own module tests all pass. I've rerun only the failed jobs on the fork (run `34791705815 --failed`, currently in_progress) rather than pushing a new head. Will report back once they finish — if they come back green the Build pointer should sync over within its normal refresh window. -- 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]
