DanielLeens commented on PR #12015: URL: https://github.com/apache/seatunnel/pull/12015#issuecomment-5867647162
@luozihen thanks for pulling the logs and asking before burning more retries - please stop retrying, it will not help. **This is deterministic, not flaky.** `Can't get Docker image ... quay.io/minio/minio:RELEASE.2024-06-13T22-53-53Z` means the MinIO test image that the S3-based ITs were pointing at is no longer pullable anonymously (Docker Hub `minio/minio` went away first, then the quay.io copy). Every run that reaches an S3/MinIO-based IT fails at container start, regardless of your code. Nothing in this PR touches those tests. **It is already fixed on `dev`, and your branch does not have the fix yet.** I checked the current heads directly: - `dev` no longer references `quay.io/minio/minio:RELEASE...` anywhere. The S3/MinIO ITs (S3FileWithFilterIT, the Hudi, Iceberg and Paimon S3 ITs, the Databend ITs and others) now use a digest-pinned public mirror of MinIO (10 files), which came in with #12297, and #12478 additionally waits for MinIO readiness in S3FileWithFilterIT. - Your head (`00acc23a5`) is 60 commits behind `dev` and still has the old tag in 9 test files, so `all-connectors-it-2 (8/11)` will keep failing until the branch picks up those changes. **Next step (lowest cost):** please sync your branch with the latest `dev` (merge or rebase, whichever you prefer) and push, then let CI run on the new head. Please do not edit any of the MinIO test files in this PR yourself - the sync brings the correct versions in. If `all-connectors-it-2` still fails after the sync, paste the new failing job link here and I will look at it against the updated head. Your source-side review status is unchanged: I have no new code-side blocker on this PR, the remaining gate is CI on a synced head. -- 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]
