DanielLeens commented on PR #11503: URL: https://github.com/apache/seatunnel/pull/11503#issuecomment-5649667925
CI status (maintainer triage, not a review of the change): the Build on `e25c5c02ac3` (the previous empty retrigger) finished with 12 failed jobs. Traced each one individually; none are caused by this PR's diff: **Widespread Docker Hub `minio/minio` pull-denied (8 jobs, one root cause):** every job failed at container `startUp()` with `ContainerFetchException: Can't get Docker image ... pull access denied for minio/minio, repository does not exist or may require 'docker login': denied` — before any test/PR logic ran: - `all-connectors-it-2` (8, 11): `IcebergSourceIT` - `all-connectors-it-6` (8, 11): `DatabendIT`, `DatabendCDCSinkIT` - `all-connectors-it-7` (8, 11): `S3FileWithFilterIT` - `paimon-connector-it` (8, 11): `PaimonWithS3IT` Note on `DatabendIT`/`DatabendCDCSinkIT`: this PR *does* touch `DatabendSinkWriter`/`DatabendSinkAggregatedCommitter` (the `runtimeRowType` schema-restore plumbing), so I traced these two specifically rather than assuming they're unrelated. Both failed in `startUp()` on the minio image pull, before the sink writer code under test ever ran — same infra cause as the other 6 jobs above, not a regression in the sink changes. **Other 4, previously-tracked/unrelated:** - `all-connectors-it-4 (11)`: `AzureCosmosDBSourceIT` — `IllegalState` inside `AbstractAzureCosmosDBIT.readRows`; this branch doesn't touch the Cosmos DB connector. - `rocketmq-connector-it (8)`: the known topic-route race (`MQClientException: No topic route info` / `broker not exist`), source fix open as #12115; this branch doesn't touch the RocketMQ connector. - `engine-v2-it (8)`: `SplitClusterFaultToleranceIT#testStreamJobCancelResolvesWhenWorkerCrashesBeforeCancelAck` and `BackpressureSlowSinkIT#testCheckpointsKeepCompletingUnderSustainedBackpressure` — the same timing-sensitive fault-tolerance/backpressure tests flagged as unrelated in earlier rounds on this PR. - `engine-v2-it (11)`: `CheckpointCoordinatorFailoverIT#testStreamJobFailsAfterCheckpointTriggerDispatchFailure` — failure is inside `CheckpointCoordinator`/`CheckpointManager`/`JobMaster` (task-group-address resolution during `notifyCheckpointCompleted`), none of which this PR modifies. The only engine-server file this branch touches is a 3-line unrelated change in `CoordinatorService#processPendingJobCleanup` (pending-job cleanup rescheduling), which has no path to this test's failure. Retriggered CI the same way as the prior rounds — fork job reruns need fork admin rights I don't have here, so via an empty commit: `30d4daaf75c` (no source change), pushed on top of the unchanged `e25c5c02ac3` tree. New Build run is in progress on that head now. -- 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]
