li3zhi4 commented on PR #11633: URL: https://github.com/apache/seatunnel/pull/11633#issuecomment-6214279806
Current-head follow-up for @SEZ9 and the maintainers: head `c93535365ab74a26ae8e7bd7569474722bcf5700` is unchanged. DanielLeens re-reviewed this exact head on October 13 and reported no source-level blocker or remaining recommended fix (https://github.com/apache/seatunnel/pull/11633#pullrequestreview-5502269166). I reran only failed jobs, not the full Build. Fork run 38382223265 attempt 4 has completed with failure; the failing lanes reported by the Jobs/check-suite APIs are: - JDK 17: https://github.com/li3zhi4/seatunnel/actions/runs/38382223265/job/116876237930 - JDK 11: https://github.com/li3zhi4/seatunnel/actions/runs/38382223265/job/116876238105 Both are `all-connectors-it-2`. This update does not establish their root cause, and I am not claiming a green required Build. @SEZ9, could you re-check the current head against the earlier change request and identify anything still missing? Once CI is green, a write-enabled maintainer will also need to provide the normal valid approval / dismissal of superseded reviews and merge-queue handling. I have not changed workflow checks or branch protection, and comment-level acceptance is not being treated as approval. -- 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]
