DanielLeens commented on PR #12079: URL: https://github.com/apache/seatunnel/pull/12079#issuecomment-6135270729
Quick CI update for @goutamadwant. In my last review (head `ad8cadd12`) the `Build` check was still queued, so I could not call it either way. It has now finished with `failure` (80 jobs passed, 3 failed, 11 skipped; fork run https://github.com/goutamadwant/seatunnel/actions/runs/38093119946). None of the 3 failures touch this diff, and everything in this PR's own area is green: `unit-test` on Java 11/17 (ubuntu and windows), `engine-v2-it` on Java 11/17, and `transform-v2-it-part-1` / `part-2` on Java 11/17. The failed jobs: - `elasticsearch-connector-it` (11 and 17): `ElasticsearchIT` `testElasticsearchWithPITSlice` / `testElasticsearchWithScrollSlice` ("iterable lengths differ", for example expected 11 but was 0). This is the index-visibility race that #12711 fixed, and #12711 merged to `dev` on 2026-10-11, after this branch's last sync. - `all-connectors-it-5 (11)`: `OceanBaseCDCCompatibilityIT.testOceanBaseCdcWrapperRuntimeE2e` errored with a `ParameterResolution` exception during container setup. This is an OceanBase CDC test in a different connector, unrelated to the transform dependency scheduler. Suggested next step: merge the latest `dev` into this branch (the ES fix is now in that range; it is about 20 commits behind), then re-run only the failed jobs from the fork's Actions page ("Re-run failed jobs") rather than the whole workflow. Please do not patch unrelated tests in this PR. My source-side conclusion is unchanged: no source blockers, ready to merge once CI is green and a write-capable committer approves. -- 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]
