SEZ9 commented on PR #12208: URL: https://github.com/apache/seatunnel/pull/12208#issuecomment-6537587208
Thanks @88fantasy for the update. A rerun of only the previously affected jobs on the unchanged head `fb4fd89ff46e8f93e3bf499702a8ccb5db91a052` is exactly the diagnostic step that was asked for. I have not independently re-checked attempt 2 of the fork [Build](https://github.com/88fantasy/seatunnel/actions/runs/40477948026) ([unit-test (11, ubuntu-latest)](https://github.com/88fantasy/seatunnel/actions/runs/40477948026/job/123900333354), [all-connectors-it-3 (11, ubuntu-latest)](https://github.com/88fantasy/seatunnel/actions/runs/40477948026/job/123900333265)) or its logs, so I am not recording those results here as a verified gate snapshot. If those jobs completed without a repeat of the `JobStateCleanupDelayTest` "Node failed to start / Address already in use" setup error seen in job 122104731061, that is consistent with the earlier failure being a startup/port flake rather than something introduced by this PR, and no test patch or unrelated dependency change is requested from you. My earlier source conclusion for the reviewed scope is unchanged. I have READ permission on the repository only, so I cannot provide the approval required by branch protection; that remains with a write-capable maintainer. Nothing further is needed from you on the CI item. <!-- streview-comment:2153 --> -- 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]
