DanielLeens commented on PR #12974: URL: https://github.com/apache/seatunnel/pull/12974#issuecomment-6396509762
Thanks for enabling Actions and sharing the results, @SiriusTL666! I checked the run directly: [fork Build 40152563142](https://github.com/SiriusTL666/seatunnel/actions/runs/40152563142) completed successfully on `ef9d5526922b153a99d06601388e933ec4c3344f`, which is still the PR head. Apache's required [Build check](https://github.com/apache/seatunnel/runs/121047417173) is now successful as well. The applicable unit-test matrix and updated-module integration jobs passed; the other integration suites were skipped by the module filter, so I am not counting those as executed tests. This supersedes the CI blocker in my previous review: CI was the only item listed under must-fix blockers, and it has now cleared. The earlier connector/test/documentation suggestions remain non-blocking observations from that review. You do not need another manual workflow trigger for this head, and there is no evidence here that a base sync is needed to resolve CI. My technical conclusion is now non-blocking. GitHub still reports `REVIEW_REQUIRED` / `BLOCKED`; I have read-level repository permission, so a maintainer with write access must provide the effective final approval. This reply is not an `APPROVED` review. Thanks again for following through! -- 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]
