DanielLeens commented on PR #11653: URL: https://github.com/apache/seatunnel/pull/11653#issuecomment-5379435342
CI follow-up (2026-08-22): in my 2026-08-21 comment I flagged that the fresh `dev`-merge Build run (`zhangshenghang/seatunnel` run `32382828114`) had failed across four jobs, root-caused each as an unrelated-module flake/infra issue (Pulsar dependency network reset, a Windows filesystem-watcher timing flake in `seatunnel-edge-agent-connector`, and two unrelated connector E2E failures), and recommended simply re-running the four failed jobs. Re-checked live: the head is unchanged (`a5164b877699ea6f92f675e354236c33bca8fe58`), and that same run now shows a clean `success` conclusion, along with the Apache-side `Build` check. So this was exactly the CI noise diagnosed, not a regression, and it's now resolved. No change to my source-level conclusion from the 2026-08-10 review: no blockers, ready to merge from my side. -- 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]
