DanielLeens commented on PR #13081: URL: https://github.com/apache/seatunnel/pull/13081#issuecomment-6646049667
Thanks @sharpca for digging into both failures, and for confirming the `--checkpoint-history-status` path. I checked it at `cac71da1`: `ClientExecuteCommand.java:329` uses `CheckpointStatus.valueOf(status.toUpperCase(Locale.ROOT))`, and `ClientExecuteCommandCheckpointStatusTest` is in the PR, so I agree no separate issue is needed. On CI: my approval stands. It was based on [run 41673624221](https://github.com/sharpca/seatunnel/actions/runs/41673624221), which completed green on this exact head, and the head has not changed since. Your read of the later run 41785719208 matches what I see. In `all-connectors-it-5`, `TiDBCDCIT` fails in `startUp` with a container `CommunicationsException`, which is environmental; this PR does not touch the TiDB CDC connector. `unit-test (17)` stopped mid-step on the runner side, with no test report. The apache-side `Build` check currently points at the failed run 41785719208. Attempt 2 of [run 41881173697](https://github.com/sharpca/seatunnel/actions/runs/41881173697) is in progress. If it finishes green, the check should switch to green on its own. Either way, nothing more is needed from you on the code. Thanks again! -- 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]
