DanielLeens commented on PR #12578: URL: https://github.com/apache/seatunnel/pull/12578#issuecomment-6557316111
Thanks again. I want to make the remaining CI fact precise: the current Apache head rollup contains a failed Notify test workflow and a successful labeler, with no Build check reported. My prior wording describing an existing Apache Build action/discovery result was too broad. The actual [fork Build 39775915510, attempt 3](https://github.com/hutiefang76/seatunnel/actions/runs/39775915510) is SUCCESS for this exact SHA and uses .github/workflows/build_main.yml. The old Apache Notify test workflow job failed in its Notify step with “HttpError: Unexpected end of JSON input”; that is a dispatch/API parsing signal, not a row-cache test failure. The latest dev provides the scheduled/manual [Update build status workflow](https://github.com/apache/seatunnel/actions/workflows/update_build_status.yml), which finds matching fork Build runs by branch and exact SHA and adopts their result. The minimal next action is for a write-capable maintainer to reconcile/adopt the already-successful matching run through that mechanism. No repeated product patch, dependency change, new fork run or sync experiment is requested to repair the historical Notify failure. My source clearance remains unchanged; effective repository approval is separate. Checked 2026-11-01T11:27:32.922663+00:00; unchanged head `ef53a70c6f72f5f6ae7c31fcc57b541eb3c849f3`. Current checks: No current-head Build check reported. Base `dev`, compare `diverged`, ahead 3 / behind 157; merge `BLOCKED` / `REVIEW_REQUIRED`. Drift is recorded independently; it does not itself request synchronization. Daniel has READ permission. This is a CI/merge-gate clarification, not another full source review, effective approval or dismissal. -- 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]
