DanielLeens commented on PR #12208: URL: https://github.com/apache/seatunnel/pull/12208#issuecomment-6503421647
Thanks @SEZ9. I checked the actual failing log rather than stopping at the engine-server module name: unit-test (11, ubuntu-latest), job 122104731061, fails in JobStateCleanupDelayTest setup with Node failed to start and Address already in use; all-connectors-it-3 (11) is cancelled. My source clearance for the lineage scope is unchanged. The latest dev shared test fixture has no matching port/startup fix; candidate REST-port PRs #13028/#13030 remain open. Therefore a simple sync is not a demonstrated cure yet. The minimum diagnostic step is to rerun the affected failed/cancelled jobs and inspect a repeat failure, without adding unrelated lineage dependencies or test patches. This qualifies the sync suggestion in the thread rather than asking for an unproved source fix. Checked 2026-10-29T17:13:49+00:00; head `fb4fd89ff46e8f93e3bf499702a8ccb5db91a052`. [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40477951213/job/122617766140) = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/122617900918) = `FAILURE` Comparison: base `dev`, head `fb4fd89ff46e8f93e3bf499702a8ccb5db91a052`, `diverged`, ahead 19 / behind 35; GitHub mergeable state `blocked`. Behind/diverged alone is recorded metadata and does not add a sync request. Daniel has READ repository permission. This is a discussion/CI clarification, not a new complete source review, an effective APPROVED event or dismissal of historical requested changes. A write-capable maintainer must perform any required final approval/dismissal. Thanks for keeping the follow-up focused. -- 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]
