DanielLeens commented on PR #13063: URL: https://github.com/apache/seatunnel/pull/13063#issuecomment-6514189541
Thanks again for the contribution. The CI fact cited previously has changed: the queued signal has completed, and the exact-head Build is now failing. The executed `edge-agent-it (11, ubuntu-latest)` lane fails while running engine-server unit tests: `JobMasterTest.before:128` reports `Node failed to start!` after its 300-second setup window. The Kafka lane also ends with failure, but the returned log ends during JVM diagnostic output without an attributable test assertion, so I am not assigning it a speculative cause. The latest dev changes since the previous audit do not fix these shared startup fixtures; #13028 and #13030 are still open. A simple base sync is not an established cure. Please rerun only the failed jobs and retain startup/runner diagnostics if they repeat; no unrelated locale-normalization patch is requested. The existing JDBC integration-coverage and bilingual-behavior-documentation requests in my complete review remain open independently of CI. Snapshot 2026-10-30T03:23:54.060709+00:00: head `3755991a1268e42a0c780c90cd5e0369fa96e629`; [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40911861985/job/123581658530) = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/123661357004) = `FAILURE`. Base `dev`; comparison `diverged`, ahead 1, behind 3; merge state `blocked`. Behind/diverged alone is recorded metadata and does not add a sync request. This is an unchanged-head discussion/CI clarification, not a new complete source review, an effective approval or a dismissal of historical requested changes. -- 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]
