SEZ9 opened a new issue, #12344: URL: https://github.com/apache/seatunnel/issues/12344
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. (Searched for both `OpengaussCDCIT` and `testAddFieldWithRestore`; no existing report.) ### What happened `OpengaussCDCIT.testAddFieldWithRestore` fails on every CI run of the `all-connectors-it-2` job on current `dev`, on both JDK 8 and JDK 11. It is not intermittent: across two unrelated pull requests, two different base commits, and four rerun attempts each, it has failed **24 of 24 legs** with no single pass. Because `all-connectors-it-2` is part of the `Build` workflow โ the only required status check on `refs/heads/dev` โ any pull request whose change set schedules that job currently cannot reach a green `Build`, regardless of what it changes. **Evidence.** These are runs of two unrelated Zeta pull requests, #12298 (`JettyService` constructor + one `HttpConfig` field) and #12299 (REST log-content reading), neither of which touches CDC, PostgreSQL, or openGauss: | Run | Base | JDK 8 | JDK 11 | |---|---|---|---| | [34926657845](https://github.com/SEZ9/seatunnel/actions/runs/34926657845) (#12298) | `0d9f9e230` | failed 4/4 attempts | failed 4/4 attempts | | [34993525332](https://github.com/SEZ9/seatunnel/actions/runs/34993525332) (#12298) | `75b60fa14` | failed 4/4 attempts | failed 4/4 attempts | | [34993534806](https://github.com/SEZ9/seatunnel/actions/runs/34993534806) (#12299) | `75b60fa14` | failed 4/4 attempts | failed 4/4 attempts | The failure is always the same assertion at the same line, and the other 14 tests in the class pass every time (`Tests run: 15, Failures: 0, Errors: 1`). I have not bisected which change introduced it, and I am not proposing a cause โ reporting it because the 100% failure rate makes it a hard blocker for unrelated work rather than background flakiness, and because nothing in the tracker covers it yet. ### SeaTunnel Version `dev` @ `75b60fa14` (3.0.0-SNAPSHOT), also reproduced on `0d9f9e230`. ### SeaTunnel Config ```conf Not applicable - this is an e2e test failure in CI, not a job configuration problem. The configuration used is the one built into OpengaussCDCIT. ``` ### Running Command ```shell # As run by the all-connectors-it-2 job of the Build workflow: ./mvnw -B -T 1C verify -pl :connector-cdc-opengauss-e2e -am -DskipUT=true -DskipIT=false ``` ### Error Exception ```log [ERROR] Tests run: 15, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 638.34 s <<< FAILURE! - in org.apache.seatunnel.connectors.seatunnel.cdc.postgres.OpengaussCDCIT [ERROR] testAddFieldWithRestore{TestContainer}[1] Time elapsed: 89.482 s <<< ERROR! org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.seatunnel.connectors.seatunnel.cdc.postgres.OpengaussCDCIT Multiple Failures (1 failure) org.opentest4j.AssertionFailedError: actual iterable was <null> at index [1][4] within 1 minutes. at org.apache.seatunnel.connectors.seatunnel.cdc.postgres.OpengaussCDCIT.testAddFieldWithRestore(OpengaussCDCIT.java:476) Caused by: java.util.concurrent.TimeoutException at org.apache.seatunnel.connectors.seatunnel.cdc.postgres.OpengaussCDCIT.testAddFieldWithRestore(OpengaussCDCIT.java:476) [ERROR] Errors: [ERROR] OpengaussCDCIT.testAddFieldWithRestore:476 ยป ConditionTimeout Assertion condit... [ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.22.2:verify (default) on project connector-cdc-opengauss-e2e: There are test failures. ``` `actual iterable was <null> at index [1][4]` means the expected row is absent rather than wrong: after the DDL is applied and the job is restored, the awaited snapshot never reaches the expected size within the one-minute window. Whether that is a product bug in restore-after-schema-change or too short a wait in the test, I can't say from the log alone. ### Zeta or Flink or Spark Version Zeta (SeaTunnel Engine), 3.0.0-SNAPSHOT. ### Java or Scala Version Reproduced on both JDK 8 and JDK 11 (`ubuntu-latest` GitHub runners). ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! I don't know this connector's restore path well enough to propose a fix, so I would rather report it than guess. Happy to run experiments on the two branches above if that helps someone who does. ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
