li3zhi4 commented on PR #11677:
URL: https://github.com/apache/seatunnel/pull/11677#issuecomment-5248786758
@DanielLeens @SEZ9 — CI on head `779c961f3` ran the full
`connector-cdc-mysql-e2e` module (107 tests) and the **single failure is not
from this PR**:
```
[ERROR]
MysqlCDCWithFlinkSchemaChangeIT.testMysqlCdcWithSchemaEvolutionCase:130
->assertSchemaEvolutionForAddColumns:256 » ConditionTimeout
[ERROR] Tests run: 107, Failures: 0, Errors: 1, Skipped: 0
```
- `MysqlCDCWithFlinkSchemaChangeIT` is a **pre-existing Flink-only
schema-change test** (disabled for SPARK/SEATUNNEL); this PR does not touch
that file at all (empty diff), and its last change predates this PR
(`12ab1d077` "Stabilize flaky connector E2E tests").
- The PR's own e2e `MysqlCDCIT#testMysqlCdcContinuesAfterSinkFailure`
**passed** on the same CI run (the only error is the Flink schema-change test
above).
- The failure is a `ConditionTimeout` in
`assertSchemaEvolutionForAddColumns`, consistent with the known flakiness of
Flink schema-evolution e2e on loaded CI runners (the test class already carries
comments about XA recover/rollback restarts on loaded runners).
So the red Build is an unrelated flaky E2E, not a regression from this PR.
Happy to rerun the failed jobs if the project prefers a green gate before
merge; the production fix, unit test, and this PR's e2e all pass on the same
run.
--
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]
