SEZ9 commented on PR #11545: URL: https://github.com/apache/seatunnel/pull/11545#issuecomment-5366246403
Thanks @DanielLeens for the thorough follow-up across both rounds — the job-by-job breakdown of run `32320672650` is exactly the level of signal we needed here. On the sync: good to see `fb62d179bd5` merged `apache/dev` in, and your confirmation that nothing in the PR's own files moved between `b16d233d846` and the current head (`fb62d179b`) means we don't need another full pass — the earlier findings stand as re-verified. On the CI result, I agree with your read: 1. **PythonIT / base image (your Issue 21)** — this is the blocker. The swap from `seatunnelhub/openjdk:8u342` to `eclipse-temurin:11-jdk` in `seatunnel-dist/src/main/docker/Dockerfile` silently dropped `python3`, and the deterministic failure on both `all-connectors-it-5 (11, ubuntu-latest)` and `all-connectors-it-5 (17, ubuntu-latest)` with `python.executable does not resolve to an executable file: /usr/bin/python3` confirms it's PR-caused, not flake. Concrete ask: install `python3` explicitly in the Dockerfile (in both build stages if the E2E container needs it at runtime), push, and let the Python-connector lanes go green on both JDK 11 and 17 before we call this resolved. 2. **CouchbaseIT on `all-connectors-it-7 (17, ubuntu-latest)`** — since you couldn't tie it to the JDK/image change, let's treat it as unconfirmed for now. Ask: once the python3 fix lands and CI reruns, check whether it reproduces on the same lane. If it does, we'll need a closer look; if not, we'll note it as pre-existing flake. 3. **kudu-connector-it (11/17) cancellations** — agreed these are fail-fast fallout, not independent findings. They should clear once the PythonIT fix lands. So the remaining asks are: (a) the `python3` install fix in the Dockerfile, and (b) a fresh, fully-completed CI run on the new head so we can confirm PythonIT is fixed and get a clean read on CouchbaseIT. Everything else from the earlier scope looks settled. <!-- streview-comment:427 --> -- 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]
