DanielLeens commented on PR #12333: URL: https://github.com/apache/seatunnel/pull/12333#issuecomment-6109460143
Hi @wgzhao, a quick follow-up on the CI note in my last review (head `eaa91181c`, which has not changed). One part of that advice is now outdated, so I want to correct it before you spend more reruns. **What I said:** the only red jobs were `elasticsearch-connector-it (11)` and `(17)`, unrelated to this PR, and the cheapest step was to rerun just those two jobs. **What I see now:** - Your fork run (`Build`, run attempt 4) is still failing in exactly the same two jobs, and the same cases: `ElasticsearchIT#testElasticsearchWithScrollSlice` and `testElasticsearchWithPITSliceQueued` (e.g. `iterable lengths differ, expected: <11> but was: <0>`). Attempts 1 to 3 failed in the same two jobs, so another plain rerun of this head is unlikely to turn green. - This PR touches only the JDBC MySQL/OceanBase catalog code and `JdbcMysqlIT`; nothing on the Elasticsearch path, so I still read this as unrelated to the diff. - The test-side fix for these exact cases has just landed on `dev`: #12711 `[Test][Connector-V2][Elasticsearch] Poll for index visibility in ElasticsearchIT slice tests` (merged 2026-10-11, after my last review). It makes the slice tests poll for index visibility, like #12642 did for the other reads, and your head does not contain it yet (the branch is currently 10 ahead / 6 behind that commit). **Suggested next step:** please sync the latest `dev` into your branch, then rerun only the failed jobs (or let the new run go through). Earlier I said that syncing would not help; with #12711 on `dev` it now should. My source-side conclusion is unchanged: no code blockers on this PR. The remaining gates are a green CI run on the synced head and the final committer approval (`reviewDecision` is still `REVIEW_REQUIRED`). Thanks for your patience! -- 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]
