DanielLeens commented on PR #10643: URL: https://github.com/apache/seatunnel/pull/10643#issuecomment-6557488283
Thanks @SEZ9. I checked the current run again: [Build](https://github.com/chl-wxp/seatunnel-laowang/actions/runs/40630477103) is still cancelled/timed out, with only the two connector-part-3 jobs unfinished: [JDK17](https://github.com/chl-wxp/seatunnel-laowang/actions/runs/40630477103/job/122626515868) and [JDK11](https://github.com/chl-wxp/seatunnel-laowang/actions/runs/40630477103/job/122626515908). This supplies concrete retry targets; it is not evidence of a port-selection assertion failure. The run owner should first check for an active newer attempt, then retry only those cancelled jobs if no execution is active. A repeated failure needs that job's actual error/log before a source change is prescribed. No matching source fix in the base has been established for cancellation, so sync alone is not a demonstrated cure. My source conclusion remains clear and the effective maintainer approval/dismissal gate remains separate. Checked 2026-11-01T11:45:12.512076+00:00; unchanged head `1d50ab8212032104e46d4f2f4b465981526802b6`, base `dev`; compare `diverged`, ahead 12 / behind 76; merge `blocked` / `BLOCKED`; review decision `REVIEW_REQUIRED`. Behind/diverged is recorded independently and does not itself request a sync. Daniel has READ repository permission. -- 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]
