DanielLeens commented on PR #12858: URL: https://github.com/apache/seatunnel/pull/12858#issuecomment-6305089474
Thanks for the clear CI update, @karthik-0306, and for asking before re-running again. I looked at the run logs, and my conclusion is that this failure is not caused by your two Python files, but re-running the same head will not make it pass, so please do not keep retrying. **What actually fails.** In the fork run for `5e77800` (run 39227503024), attempt 3 of `all-connectors-it-6 (17, ubuntu-latest)` fails with `DatabendCDCSinkIT.testDatabendSinkCDC:88` (`ConditionTimeoutException ... Expected 3 records in sink_table ==> expected: <3> but was: <0> within 3 minutes`). Attempt 1 of the same job failed on exactly the same test and assertion, so it is deterministic on this head rather than a flake. It is a Databend connector E2E, nothing in `tools/seatunnel-python-sdk` is on its path. **Why dev passes.** This symptom is the one fixed by #12848 (`Run the final Databend CDC merge when the writer closes`, merged on Oct 19 as `2bc9d0e`; its description names `DatabendCDCSinkIT` failing with `expected: <3> but was: <0>`). Your head is based on an older `dev` and does not contain that commit (the branch is 21 commits behind `dev`). One correction to the dev comparison: the scheduled `Backend` run on `dev` you linked (run 39282837181, head `03f3f3e`, which already includes #12848) passed `all-connectors-it-6` on both JDK 11 and 17. Its red jobs were `unit-test`, `engine-resource-managers-it` and `connector-redis-it`, so `all-connectors-it-6` is not currently broken on `dev`. **Attempt 1 `unit-test (11)`.** That one failed in `SavePointTest.testSavePointButJobGoingToFail` (engine module), which is also unrelated to a Python-only change. **Concrete next step:** merge (or rebase) the latest `dev` into your branch and push. That picks up #12848, and the push starts a fresh `Build` in your fork, so you do not need to re-run the old attempts. Please note that `unit-test` on current `dev` can still show a `JdbcOptionRuleCompletenessTest` failure until #12875 lands; that is also unrelated to this PR, so if `all-connectors-it-6` turns green and only that shows up, just say so here. My review of the code is unchanged: no blocking issue on the Python side, and I am happy to approve once `Build` is green on the synced head. Thank you for the careful follow-up! -- 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]
