DanielLeens commented on PR #11653: URL: https://github.com/apache/seatunnel/pull/11653#issuecomment-5364320665
CI re-check follow-up (2026-08-20): my 2026-08-10 review said CI was fully green on the head at that time (`1610a7cac100`). The picture has changed since then — this is worth a note. **What changed**: the branch was merged with `dev` today (`a5164b877699`, "Merge branch 'dev' into zsh-sync-st3517-pending-scheduler", 2026-08-20T14:53Z), which retriggered a fresh Build run: https://github.com/zhangshenghang/seatunnel/actions/runs/32382828114 (conclusion: failure). **Root-caused each failing job** — none touch `seatunnel-engine` or this PR's own diff (`CoordinatorService`/pending-job scheduling): - `unit-test (11, ubuntu-latest)` — `connector-pulsar` dependency resolution died with `Connection reset` fetching `io.kubernetes:client-java-parent:12.0.1` from Maven Central. Pure network flake, unrelated to any test. - `unit-test (11, windows-latest)` — `FileCollectReaderBehaviorTest.rediscoversFileAfterInactiveCursorClosed` in `seatunnel-edge-agent-connector` timed out (`awaitility` `expected: <1> but was: <0>` within 3s). Unrelated module, looks like a filesystem-watcher timing flake on Windows. - `all-connectors-it-3 (11, ubuntu-latest)` — `FlussSourceIT` e2e failure, unrelated connector. - `doris-connector-it (11, ubuntu-latest)` — `DorisErrorIT` e2e failure, unrelated connector. All four are independent, unrelated-module flakes/infra issues (one clear Maven Central network reset, three e2e timing flakes in connectors this PR never touches). None indicate a regression from this change. **Updated bottom line**: still no source-level blocker — this is purely a CI rerun away from green. Recommend rerunning the four failed jobs (`gh run rerun 32382828114 --failed` on the fork, or the apache-side rerun) 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]
