SEZ9 commented on PR #11602: URL: https://github.com/apache/seatunnel/pull/11602#issuecomment-6514094764
Quick follow-up on the one open gate at head `e25b3354e65afa6dec118820cb187f87f24a2a72`. [Build](https://github.com/apache/seatunnel/runs/121486172860) is still `ACTION_REQUIRED`. The blocking stage is workflow-run detection: no fork Build run was found for this exact SHA. This is not an executed test failure, so it does not implicate the source. [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40168025208/job/121480713925) is `SUCCESS`. To clear it: 1. Open the Actions tab on your fork. If workflows are shown as disabled there, enable them; otherwise skip this step. 2. Manually run the existing Build workflow on this PR branch at head `e25b3354e65afa6dec118820cb187f87f24a2a72`. 3. If a matching run for that exact head already exists, please link it here so a maintainer can reconcile the aggregate status. No empty commit, speculative dependency change, or base sync is requested just to activate CI; none of those supply the missing exact-head run, and the divergence from `dev` is recorded metadata only. Separately, the documentation correction from my [earlier review](https://github.com/apache/seatunnel/pull/11602#pullrequestreview-5643679538) remains open (the per-job JobMaster path is bounded per worker, not by one overall deadline); the unchanged head does not resolve it, and a follow-up commit for that is welcome whenever convenient. I have read permission only, so once an exact-head Build run is green, a write-capable maintainer will need to perform any final approval. <!-- streview-comment:2144 --> -- 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]
