You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@paimon.apache.org by "wombatu-kun (via GitHub)" <gi...@apache.org> on 2026/07/19 12:13:22 UTC
[PR] [flink-cdc] Stabilize MySqlSyncDatabaseActionITCase.testSyncMultipleShards [paimon]
wombatu-kun opened a new pull request, #8736:
URL: https://github.com/apache/paimon/pull/8736
### Purpose
`MySqlSyncDatabaseActionITCase.testSyncMultipleShards` intermittently fails CI with `java.util.concurrent.TimeoutException: testSyncMultipleShards() timed out after 120 seconds` (for example, it failed the CI run of an unrelated PR #8735, whose changes are confined to `paimon-common` global btree index code and cannot reach Flink CDC). This is a flaky timeout, not a functional regression.
Two things make the test prone to spurious timeouts.
First, the 120s per-method budget is tight for this test. Unlike its siblings it does several sequential `waitForResult` phases, each preceded by a schema `ALTER` that forces the CDC source to re-snapshot the changed table, on top of Flink job startup and the initial MySQL snapshot/binlog switchover. Under a loaded CI runner this legitimately exceeds 120s even though the data volume is tiny. This raises the timeout to 240s, the same value already used by the comparable heavy multi-table test in this class, `testSyncManyTableWithLimitedMemory` (the newly-added-table tests use 600s).
Second, the test called the `JobClient`-less `waitForResult` overload, in which `checkJobNotTerminated(...)` is a no-op. If the CDC job ever dies, the test cannot tell a dead job from a slow one and simply hangs until the outer `@Timeout` fires, producing an opaque timeout with no diagnosis. This captures the `JobClient` returned by `runActionWithDefaultEnv(...)` and threads it through the four `waitForResult` calls, so a terminated job now fails fast with a clear `AssertionError` instead of hanging. This matches the pattern already used by other tests in the same file (for example the newly-added-table tests).
No production code changes; test-only.
### Tests
`MySqlSyncDatabaseActionITCase.testSyncMultipleShards` (the modified test itself).
--
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: issues-unsubscribe@paimon.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [flink-cdc] Stabilize MySqlSyncDatabaseActionITCase.testSyncMultipleShards [paimon]
Posted by "JingsongLi (via GitHub)" <gi...@apache.org>.
JingsongLi commented on PR #8736:
URL: https://github.com/apache/paimon/pull/8736#issuecomment-5018497053
+1
--
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: issues-unsubscribe@paimon.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [flink-cdc] Stabilize MySqlSyncDatabaseActionITCase.testSyncMultipleShards [paimon]
Posted by "wombatu-kun (via GitHub)" <gi...@apache.org>.
wombatu-kun closed pull request #8736: [flink-cdc] Stabilize MySqlSyncDatabaseActionITCase.testSyncMultipleShards
URL: https://github.com/apache/paimon/pull/8736
--
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: issues-unsubscribe@paimon.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [flink-cdc] Stabilize MySqlSyncDatabaseActionITCase.testSyncMultipleShards [paimon]
Posted by "JingsongLi (via GitHub)" <gi...@apache.org>.
JingsongLi merged PR #8736:
URL: https://github.com/apache/paimon/pull/8736
--
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: issues-unsubscribe@paimon.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org