nzw921rx opened a new pull request, #10948:
URL: https://github.com/apache/seatunnel/pull/10948
### Purpose of this pull request
Fix flaky tests in `jdbc-connectors-it-ddl` E2E module by:
1. Increasing Awaitility timeouts that were too tight for CI environments
2. Adding a proper container wait strategy for Dameng (DM) database
**Root cause:**
The `SqlServerSchemaChangeIT` test intermittently fails with
`ConditionTimeout` in CI:
```
Error:
SqlServerSchemaChangeIT>AbstractSchemaChangeBaseIT.testMysqlCdcWithSchemaEvolutionCaseExactlyOnce:293
->AbstractSchemaChangeBaseIT.assertSchemaEvolution:298 » ConditionTimeout
Tests run: 6, Failures: 0, Errors: 1, Skipped: 0
```
The Awaitility timeouts in `assertSchemaEvolution` and related methods were
too short (30s~60s) for CI environments where CDC data sync can be slower due
to resource contention.
**Timeout changes in `AbstractSchemaChangeBaseIT`:**
- Job RUNNING status wait: 30s → 60s
- Savepoint wait: 30s → 60s
- Data sync assertions in `assertSchemaEvolution`: 60s → 120s
- Data sync assertions in `assertSchemaEvolutionForAddColumns`: 60s → 120s
- Unified time unit style from `MILLISECONDS` to `SECONDS`
**DM container fix in `DmSchemaChangeIT`:**
- Added `withExposedPorts()`, `waitingFor(Wait.forListeningPort())` and
`withStartupTimeout(5min)` to ensure DM database is fully initialized before
tests start
### Does this PR introduce _any_ user-facing change?
No. This change only affects E2E test stability.
### How was this patch tested?
These are test infrastructure changes. The fixes target known
`ConditionTimeout` failures observed in CI (e.g.
`SqlServerSchemaChangeIT.testMysqlCdcWithSchemaEvolutionCaseExactlyOnce`).
--
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]
