DanielLeens commented on PR #12057: URL: https://github.com/apache/seatunnel/pull/12057#issuecomment-5723148122
Thanks for digging into the actual failing jobs rather than just re-running and hoping. Your read matches what I'd expect from those job names: `TestFilterRowKindIT` is a known unrelated flake (and the fact that the JDK8 run and the other `part-2` runs passed on the same head supports that), and the three `ContainerFetch` failures (Databend, Iceberg-on-S3, Paimon-with-S3) are Docker-image-pull issues that have nothing to do with a Metadata Transform change — those tests don't even exercise the transform module. One thing worth checking specifically before you retrigger: if the Iceberg-on-S3 `ContainerFetch` failure is pulling `minio/minio`, that's a known, already-diagnosed infra issue (`minio/minio` was removed/relocated on Docker Hub) that was fixed upstream in #12287 by moving to `quay.io/minio/minio` — if that fix is already in `dev` and your branch hasn't picked it up yet, a sync would clear that one specifically rather than just being a lucky retrigger. The `engine-v2-it` checkpoint/Hazelcast timeouts are also consistent with ordinary CI-runner resource contention rather than anything code-related. No code-side blocker from my last review, and nothing above changes that. Go ahead and retrigger the failed jobs (or the full `Build` run if that's easier) — happy to take a final look once it's green. -- 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]
