PDGGK commented on PR #10532: URL: https://github.com/apache/seatunnel/pull/10532#issuecomment-5010198889
CI update on the current head (`a4072859`): the code-relevant lanes are green — **Code style ✅, the added `AbstractJdbcCatalogCloseTest` ✅ (2/0), and the connector-jdbc / connector-file e2e parts ✅**. The three red lanes are all unrelated to this PR's resource-leak changes and look like fork-runner infra / flakiness: - `unit-test` → `MetricsApiTest` in `seatunnel-engine-server` (a module this PR does not touch) - `kafka-connector-it` → needs a Kafka broker not available on the fork runner - `updated-modules-integration-test-part-1` → `MysqlCDCWithSchemaChangeIT` (connector-cdc-mysql, pulled in transitively via connector-jdbc); it ran ~200s then errored on a Hazelcast "connection refused" cluster start — and the `AbstractJdbcCatalog` connect/close it exercises logged cleanly, so the leak-fix change is not implicated. So none of the failures come from the changes in this PR. Since a fork cannot fully run SeaTunnel's service-dependent suite, the definitive validation would be the upstream CI run when a maintainer triggers it. Happy to rerun or adjust anything if useful. -- 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]
