sharpca commented on PR #13081: URL: https://github.com/apache/seatunnel/pull/13081#issuecomment-6680736404
Understood, and the branch stays untouched - no TiDB changes, no dev sync, nothing that would move the head away from `cac71da1e`. The green evidence for this exact head, for whoever reconciles the check: - Fork build **41881173697, attempt 2**, head `cac71da1e29ecfbbf7890286dbecbd791b732bf3`, conclusion **success**: https://github.com/sharpca/seatunnel/actions/runs/41881173697 - Attempt 1 failed only on `all-connectors-it-5 (17)` -> `TiDBCDCIT` (connection refused, then server went away); re-running that single job turned the whole run green. I tried to retrigger the adoption side myself, and it is indeed outside my permissions: ``` gh workflow run update_build_status.yml --repo apache/seatunnel --ref dev -> HTTP 403: Must have admin rights to Repository ``` The scheduled run keeps ticking successfully (latest at 08:34Z) but skips this PR because the Build check is already final for run 41785719208 - which matches exactly what you described. So the reconcile step needs someone with write access; I will not touch the branch in the meantime, and the run link above is the evidence to reconcile against. For completeness on the sibling PR: #13083 is now fully green - its Build check was adopted on head `b3209869` (Build: pass, Signal: pass), and it also only awaits a committer. -- 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]
