DanielLeens commented on PR #13037: URL: https://github.com/apache/seatunnel/pull/13037#issuecomment-6503366090
The previous pending/approval-only CI fact has changed. The exact fork run 40646284640 fails in Windows JDK 17 ApplicationLifecycleTest.driverInitializationIsBoundedByTheStartupTimeout (line 574), and edge-agent JDK 11 NestedRowAccountingTest setup fails with Node failed to start / Address already in use. The DB2 diff does not modify those fixtures. I inspected latest dev's shared startup/application tests and candidate #13028/#13030: those port-fix PRs are still open, and no matching merged cure is established. A simple sync alone is therefore not a verified resolution. Rerun the two failed jobs; if they repeat, the shared CI/test owners should address the named fixture rather than adding unrelated DB2 changes. Checked 2026-10-29T17:11:17+00:00; head `6dd8bd00f11c2bd3eac280b816bf49c1074506a3`. [Label PRs when reviewed](https://github.com/apache/seatunnel/actions/runs/40674083814/job/122838058005) = `SUCCESS`; [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40646333045/job/122796290004) = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/122810056555) = `FAILURE` Comparison: base `dev`, head `6dd8bd00f11c2bd3eac280b816bf49c1074506a3`, `diverged`, ahead 1 / behind 19; 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]
