DanielLeens opened a new pull request, #11204: URL: https://github.com/apache/seatunnel/pull/11204
## What does this PR change? This stabilizes `MysqlCDCWithSchemaChangeIT` on the Zeta path. The failing CI was timing out in `assertSchemaEvolutionForAddColumns`, but the same test class still had a mix of short hard-coded waits that assumed local-speed DDL propagation. Under loaded GitHub Actions runners, schema evolution and follow-up CDC rows can converge much more slowly. This PR: - replaces the remaining short hard-coded waits with shared schema/data timeout constants - aligns the add-column and structure/data waits with the slower Zeta CI behavior - relaxes the timestamp drift assertion from `3s` to `60s`, matching the existing Flink schema-change IT tolerance for `current_timestamp()` defaults ## Why is this needed? `#11183` exposed a shared failure in: - `MysqlCDCWithSchemaChangeIT.testMysqlCdcWithSchemaEvolutionCase` That failure is unrelated to the dead-link Node 22 change itself and can also block other unrelated PRs. ## How was this verified? - `JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home ./mvnw spotless:apply -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-mysql-e2e -nsu -Dmaven.gitcommitid.skip=true -T 3C` - `JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home ./mvnw -q -DskipTests verify -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-mysql-e2e -nsu -Dmaven.gitcommitid.skip=true -T 3C` I could not run the Testcontainers E2E locally in this worktree because the local Docker daemon was unavailable (`Cannot connect to the Docker daemon at unix:///Users/stone/.docker/run/docker.sock`). -- 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]
