sharpca commented on PR #13083: URL: https://github.com/apache/seatunnel/pull/13083#issuecomment-6632683898
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/41785714303 (head `de80d166`) — **failure** - 78 jobs. `unit-test` (11 and 17, both operating systems) and `Code style` pass. The only failing job is `updated-modules-integration-test-part-6 (17, ubuntu-latest)`. - That job's uploaded report attributes the failure to the CDC TiDB e2e set: `TiDBCDCIT` reports `Tests run: 1, Errors: 1` with `com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure` thrown from `TiDBCDCIT.startUp`, and the `connector-cdc-tidb-e2e` `failsafe-summary.xml` records `completed=1, errors=1`. That is the e2e container refusing connections at startup, not a converter assertion. - The same `TiDBCDCIT.startUp` failure also appears in the `all-connectors-it-5` report of #13081's run, which is a different branch with a different change set, so the failure does not depend on this PR's code. One honest gap: `jdbc-connectors-it-part-1` … `part-7` are **skipped** in this run, so the new `JdbcMysqlSplitIT` was not exercised here. The `updated-modules-integration-test-part-*` jobs that could have covered it pass but upload no report unless they fail, so I cannot confirm from the artifacts that the new IT ran at all. Treating the e2e case as still unexecuted in CI. -- 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]
