DanielLeens commented on PR #12578: URL: https://github.com/apache/seatunnel/pull/12578#issuecomment-6503414599
The old Notify-test-workflow failure guidance is stale. I found a successful exact-head fork Build (39775915510, attempt 3), while the current Apache Build aggregate remains an action/discovery gate. The next action is for a maintainer to reconcile/adopt that existing matching run, rather than have the contributor change row-cache code, dependencies or repeatedly sync to chase an obsolete notification failure. Source clearance remains unchanged; the effective review gate is separate. Checked 2026-10-29T17:13:29+00:00; head `ef53a70c6f72f5f6ae7c31fcc57b541eb3c849f3`. [Notify test workflow](https://github.com/apache/seatunnel/actions/runs/38787676286/job/116603788523) = `FAILURE`; [labeler](https://github.com/apache/seatunnel/actions/runs/38787676256/job/116603786377) = `SUCCESS` Verified matching fork evidence: [Build run 39775915510](https://github.com/hutiefang76/seatunnel/actions/runs/39775915510), attempt 3, `success`. Repository aggregate/adoption and effective approval remain separately evaluated. Comparison: base `dev`, head `ef53a70c6f72f5f6ae7c31fcc57b541eb3c849f3`, `diverged`, ahead 3 / behind 141; GitHub mergeable state `blocked`. Behind/diverged alone is recorded metadata and does not add a sync request. Daniel has READ repository permission. This is a discussion/CI clarification, not a new complete source review, an effective APPROVED event or dismissal of historical requested changes. A write-capable maintainer must perform any required final approval/dismissal. Thanks for keeping the follow-up focused. -- 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]
