SEZ9 commented on PR #11597: URL: https://github.com/apache/seatunnel/pull/11597#issuecomment-5673822424
Thanks for the update and for the detailed CI breakdown. To summarize where I think this stands on the one point that's been raised: The diff at `07510c5530e6` is reported as byte-for-byte identical to what was reviewed at `2995a72ff664`, with only a `dev` merge landing in between that touched none of the PR-owned files. That means the review conclusions on the endpoint itself (`RunningJobSlotUsageBuilder` aggregation, master-forwarding via `GetRunningJobSlotUsageOperation`, v1/v2 servlet wiring, `slotSourceAvailable` signal) carry over unchanged. On the `Build` `FAILURE` at `07510c5530e6` (run `34763554737`): none of the three failing categories appear to touch code this PR owns. - `S3FileConnectDryRunIT` in `all-connectors-it-7`: this is attributed to the branch being behind `dev`, and a fix for exactly this failure mode is already on `dev`. - `SplitClusterFaultToleranceIT` / `CheckpointCoordinatorFailoverIT` in `engine-v2-it`: pre-existing Zeta fault-tolerance suites, not exercised differently by a read-only REST endpoint. - `OpengaussCDCIT.testAddFieldWithRestore` in `all-connectors-it-2`: reported as also failing on an unrelated PR the same day, so likely environmental. Concrete asks before I can move this forward: 1. Please merge the latest `dev` into this branch — that should clear the `S3FileConnectDryRunIT` failure on its own — and push so CI reruns on the new head. 2. If `engine-v2-it` or `all-connectors-it-2` still fail after the sync, please rerun those jobs once more in isolation before we dig further; both suites are timing-sensitive under CI load, and I'd like a clean signal before attributing anything to this diff. 3. Once you have a green run on the new head, drop a note here with the run link so I can confirm the PR-owned files are still unchanged relative to what was reviewed. The earlier comment also mentions a separate non-CI blocker, but that part of the thread is cut off on my end. Could you restate what that outstanding item is so we're working from the same list? <!-- streview-comment:1055 --> -- 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]
