DanielLeens commented on PR #11812: URL: https://github.com/apache/seatunnel/pull/11812#issuecomment-5364322554
CI re-check follow-up (2026-08-20), as promised in my 2026-08-19 review: the fresh Build run on the empty retrigger commit (`e76825af`) has completed — https://github.com/goutamadwant/seatunnel/actions/runs/32235275368 (conclusion: failure). Traced both failing jobs: - `transform-v2-it-part-1 (8, ubuntu-latest)` — never got past the setup step. `./mvnw` tried to fetch `maven-wrapper-3.1.0.jar` from `repo.maven.apache.org` and got `403 Forbidden`, so `Could not find or load main class org.apache.maven.wrapper.MavenWrapperMain` and the job aborted before compiling or running a single test. - `connector-redis-it (8, ubuntu-latest)` — same failure mode, same URL, `429 Too Many Requests` instead of `403`. Both are Maven Central rate-limiting/connectivity issues hitting the runner before any code from this PR (or any test) executes — nothing to do with the classloader-release fix. This matches the same window of Maven Central flakiness other PRs saw today. **Updated bottom line**: still no source-level blocker, still just a CI rerun away from green — the retrigger simply landed in a bad window for `repo.maven.apache.org`. Recommend a job-level rerun of these two jobs rather than treating this as a new issue. -- 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]
