sharpca commented on PR #13081: URL: https://github.com/apache/seatunnel/pull/13081#issuecomment-6632684713
Fork Actions had been disabled at the repository level; it is enabled again and I dispatched the workflow, so the PR check now reports the fork run for the current head. - Run: https://github.com/sharpca/seatunnel/actions/runs/41785719208 (head `cac71da1`) — **failure** - 96 jobs; two failing: `unit-test (17, ubuntu-latest)` and `all-connectors-it-5 (17, ubuntu-latest)`. - `all-connectors-it-5`: the uploaded report shows `TiDBCDCIT` failing with `Tests run: 1, Errors: 1` and `com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure` from `TiDBCDCIT.startUp` — the same e2e container-startup failure that #13083's run shows, on a branch with a different change set. - `unit-test (17)`: every step is reported as successful while the job is marked failed, and that job uploaded no report, so I cannot state its cause from the artifacts. The same job also failed on this branch's earlier commit `24c2d878` (run https://github.com/sharpca/seatunnel/actions/runs/41675888169), so it is not specific to the current head. On `--checkpoint-history-status`: it is fixed in this PR at `cac71da1`, not deferred. `ClientExecuteCommand` parses it with `CheckpointStatus.valueOf(status.toUpperCase(Locale.ROOT))`, and `ClientExecuteCommandCheckpointStatusTest` covers `failed` and `in_progress` under `tr-TR`, restores the base, `DISPLAY` and `FORMAT` locale defaults, and carries `@ResourceLock("java.util.Locale")`. No separate issue is needed. -- 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]
