SEZ9 commented on PR #11597: URL: https://github.com/apache/seatunnel/pull/11597#issuecomment-6594322410
Thanks for the update on the CI gate. On the cancelled run: agreed that fork run 41162604738 on `38f1ca01d7bace05a0dec8627c5143f6002ddca6` (`completed` / `cancelled`, success=7, cancelled=77, skipped=12) gives us no executed evidence either way, and since nothing in the retrieved metadata explains the cancellation, there is no reason to treat it as a failure or a pass. Given that `e3a5965c54d` has now been pushed, I'd rather not spend time re-running the cancelled jobs on the old head; a full run on the new head is the right call. Concrete asks: 1. Let fork run 41568689622 on `e3a5965c54d` complete, then post the final conclusion here, including per-job counts as before, so the record on this thread reflects actual executed results rather than the queued state. If it is cancelled again, please check for a newer attempt before resuming only the cancelled required jobs. 2. Please confirm the diff between `38f1ca01d` and `e3a5965c54d` is comment-only, as described, so the CI result on the new head can be read as covering the same logic that was reviewed on `38f1ca01d`. 3. Keep any further pushes to this head free of unrelated source or dependency edits until that run finishes, so we don't lose the CI signal again. Once 41568689622 reports, I'll take another look at the gate status. <!-- streview-comment:2246 --> -- 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]
