DanielLeens commented on PR #11012: URL: https://github.com/apache/seatunnel/pull/11012#issuecomment-4758088859
Hi @lazyfetch, I rechecked the current fork CI on the same head. The red items are now split into three buckets: 1. `updated-modules-integration-test-part-1`: `SqlServerSchemaChangeIT.testMysqlCdcWithSchemaEvolutionCaseExactlyOnce` times out in the JDBC schema-evolution suite. That is outside the Sybase connector path. 2. `updated-modules-integration-test-part-2`: `JdbcDb2UpsertIT.testDb2UpsertE2e` fails on a timestamp assertion differing only at the microsecond tail. That is also outside the Sybase connector path. 3. `updated-modules-integration-test-part-4`: `JdbcSybaseIT` is red because the Sybase Testcontainers image itself does not come up cleanly. The concrete error is `ContainerLaunchException: Timed out waiting for container port to open (localhost ports: [5000] should be listening)` after `nguoianphu/docker-sybase:latest` crashes during startup. So from Daniel's side I still do not see a new source-level blocker in the dialect / mapper / row-converter path itself, but this branch is not merge-ready yet because the PR's own Sybase E2E lane is still red. The lowest-cost next step is not to change the JDBC source logic again; it is to stabilize or replace the Sybase test-container startup path so `JdbcSybaseIT` can run cleanly, then rerun the build. -- 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]
