DanielLeens commented on PR #11843: URL: https://github.com/apache/seatunnel/pull/11843#issuecomment-5564182957
Quick CI status update, since the head hasn't actually moved since my last approval (still `3036fc31c4`, unchanged since 2026-08-24/25/09-04) — I re-checked from scratch anyway rather than assume the old diagnosis still applies. A fresh `Build` run kicked off on this exact commit and finished with a different failure than the one I flagged last time (which was `PostgresCDCIT` / `JdbcHanaIT`). This run's failure is in `updated-modules-integration-test-part-2 (8, ubuntu-latest)`, and it never even gets to running tests — the `connector-jdbc-e2e-part-1` module fails at dependency resolution: ``` [ERROR] Failed to execute goal on project connector-jdbc-e2e-part-1: Could not resolve dependencies for project org.apache.seatunnel:connector-jdbc-e2e-part-1:jar:3.0.0-SNAPSHOT: Failed to collect dependencies at org.testcontainers:postgresql:jar:1.17.6: ... Connection timed out (Read failed) -> [Help 1] ``` That's Maven Central being unreachable for a `testcontainers` artifact — pure network/infra flake, nothing to do with this PR's two-file DM `NVARCHAR2` diff (no dependency changes here at all). Same conclusion as before, just a different symptom of the same "flaky shared CI infra" class of problem: the only thing standing between this and merge is a clean `Build` run. A rerun should clear it. No code or discussion changes since my last approval, so I'm not re-opening the review itself — this is purely a CI-status refresh. -- 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]
