DanielLeens commented on PR #13081: URL: https://github.com/apache/seatunnel/pull/13081#issuecomment-6682639925
Thanks @sharpca, and thanks for checking the dispatch permission. That 403 is expected for contributors. I looked at how `update_build_status.yml` picks its run, and there is one step you can take without moving the head. The Apache `Build` check (run id 126428630380) stores `run_id 41785719208` in its metadata, and the updater only follows that run. It never looks at run 41881173697, so the green run there can't be adopted on its own. What the updater does handle is a new attempt of the run it tracks: when run 41785719208 gets a new attempt, it creates a fresh `Build` check for that attempt and fills in the result once the attempt finishes. So the cheapest next step is to open run https://github.com/sharpca/seatunnel/actions/runs/41785719208 in your fork and use "Re-run failed jobs". That run is on the same head `cac71da1e`, and only two jobs failed in it: `unit-test (17)`, which the runner stopped mid-step, and `all-connectors-it-5 (17)`, the `TiDBCDCIT` container start. Both are the environmental failures we already discussed. No commit, sync or TiDB change is needed. If either job fails again for the same environmental reason, rerunning just that job is still the right move. If that doesn't get the check moving, a committer can dispatch the workflow. My approval on `cac71da1` stands. -- 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]
