DanielLeens commented on PR #12678: URL: https://github.com/apache/seatunnel/pull/12678#issuecomment-6473822489
Thanks for reporting exactly which local checkpoint tests you ran and distinguishing them from GitHub evidence. Those results do not replace a Build on this SHA. The aggregate now reports a workflow-discovery/action gate; that is not evidence of a failed checkpoint assertion. Please make an exact-head fork Build available using the existing workflow (enable Actions if disabled, or dispatch Build for this branch), or resolve the previously reported account restriction with GitHub. An authorized run in another repository you control can supply evidence for a maintainer to inspect. A base sync alone cannot resolve an account/workflow activation restriction; no further speculative source change is requested. Gate snapshot (2026-10-28T15:55:04+00:00), head `71ac656652f0fa3423067dc6ee1052b3b3be844a`: [Build](https://github.com/apache/seatunnel/runs/122810327224) is `ACTION_REQUIRED`. The exact blocking stage is **Build workflow-run detection**: the check says no fork Build was found for this SHA. This is not an executed test failure and does not by itself prove that fork Actions is disabled. Open the fork Actions tab, enable workflows if needed, then manually run the existing Build workflow for this PR branch. If a matching run already exists, link it for a maintainer to reconcile the aggregate. No empty commit or speculative dependency change is requested. Upstream check: current dev retains the fork-run adoption workflow and its scheduled/manual status-refresh path. A base sync alone cannot enable fork Actions or supply a missing exact-head workflow run, so I am not prescribing sync as the fix for this activation gate. My [previous source conclusion](https://github.com/apache/seatunnel/pull/12678#pullrequestreview-5681302082) remains clear for the reviewed scope. CI is not being passed by inference, and this follow-up is not an effective approval. Comparison recorded in this scan: base `dev`, `diverged`, ahead 4 / behind 7, no merge conflict. Branch drift is metadata here and is not an additional sync request. -- 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]
