DanielLeens commented on PR #11077: URL: https://github.com/apache/seatunnel/pull/11077#issuecomment-6305097816
Thanks @hesam-oxe for laying this out. I checked the Actions state for this head directly, and I think the diagnosis is a little different, so a maintainer approving a run will not unblock it. Here is what I can see for `8b383c04eeed65c41a14ba756100a33f430124eb`: - The apache-side `Build` check (https://github.com/apache/seatunnel/runs/114987916217) is not a run waiting for approval. Its conclusion is `action_required` with the title "Workflow run detection failed", and its text says the build for a PR runs in your fork and that no `Build` run was found there for this head commit. - The only apache-repo workflow run that is in `action_required` for this SHA is `Label-when-reviewed` (a `pull_request_review` labeling workflow, run 38327253670). It is unrelated to the build, so approving it would not create any `Build` evidence. - In your fork, the `Build` workflow is listed as `active`, and its `push`-triggered runs were created without any approval step for earlier commits of this branch (for example run 35497458667 for `1bfcea62`, created 2026-09-20). The most recent `Build` run in the fork is from that date, and there is none for `8b383c04`. So pushing a new commit (or starting `Build` from the fork's Actions tab on this branch, as the check output describes) should produce a fork run that the check can adopt, and that does not need a committer's approval. So I would keep my earlier suggestion, with one clarification: please trigger the fork `Build` yourself (manual run on this branch, or an empty commit after syncing the latest `dev`, since the branch is currently `diverged`, ahead 38 and behind 73), and then link the fork run here. I only have read-level rights on this repository, so I cannot approve or start any run for you. The earlier fork `Build` runs on previous heads all ended as `failure`, so a fresh run is needed anyway before we can judge the head. The code-level items I listed (collision identity fallback, pattern precedence, and the requested multi-table coverage) remain open and I will pick them up as soon as there is a runnable CI head to review against. -- 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]
