davidzollo opened a new pull request, #11608: URL: https://github.com/apache/seatunnel/pull/11608
### Why Recent dev CI had repeated Paimon E2E failures in the same negative schema test, independent of a specific PR diff: - 2026-07-28 Build run https://github.com/apache/seatunnel/actions/runs/30350787586/job/90257731539 failed in `PaimonSinkCDCIT.testSinkWithIncompatibleSchema` with a `ConditionTimeoutException`. - 2026-07-30 Schedule Backend run https://github.com/apache/seatunnel/actions/runs/30561716311/job/90942758546 failed in the same test with `st-multi-table-sink-writer-1` still running after the expected schema mismatch failure. The test already proves the user-facing Paimon schema validation error. The flake comes from applying the generic post-job thread-leak check to an intentionally failing sink initialization path. ### What - Keep the successful Paimon CDC write through `executeJob` so the target table is created and connector jars are copied into the container. - Execute the expected-failure schema mismatch config through the base SeaTunnel CLI command and keep asserting `exitCode = 1` plus the exact schema mismatch message. - Fall back to `executeJob` for test containers that do not expose base command execution. ### Verification - `./mvnw -f seatunnel-e2e/seatunnel-connector-v2-e2e/connector-paimon-e2e/pom.xml spotless:apply -nsu` - `git diff --check` Local compile/test/E2E/Docker were not run, following the SeaTunnel local verification rule for this CI-fix workflow. The final runtime verdict should come from GitHub Actions on this PR head. -- 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]
