akshar27 commented on PR #12129: URL: https://github.com/apache/seatunnel/pull/12129#issuecomment-5721103570
CI ran for the first time on this head (`408f1e0`, after enabling GitHub Actions on my fork) — it's not green, but the failure is unrelated to this PR's change. **Result**: `unit-test` (JDK 8 and 11), `engine-v2-it`, code style, and license header all pass — everything that actually exercises `PhysicalPlan`/`JobStatus`. Three jobs failed: `all-connectors-it-2` (JDK 8 and 11) and `all-connectors-it-6` (JDK 8 and 11), all Docker-based connector E2E suites this PR doesn't touch. **Root cause**, from the `all-connectors-it-2` log: ``` org.testcontainers.containers.ContainerFetchException: Can't get Docker image: minio/minio:RELEASE.2024-06-13T22-53-53Z Caused by: com.github.dockerjava.api.exception.NotFoundException: Status 404: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied ``` `IcebergSourceIT` (Iceberg-on-S3 connector) can't pull `minio/minio:RELEASE.2024-06-13T22-53-53Z` from Docker Hub — a 404/access-denied on the image itself, not a test assertion failure. My guess is this repo's CI normally authenticates to Docker Hub via a secret to avoid exactly this, and forks don't inherit repo secrets, so an anonymous pull on my fork is hitting Docker Hub's access restrictions on that image/tag. Nothing in the diff touches connector code, Docker image references, or CI config, so I don't think this is something introduced by this change — but flagging it explicitly rather than assuming, since I can't compare directly against a fork-hosted run of unmodified `dev`. Let me know if you'd like me to retrigger just those jobs, or if this is a known fork-CI gap on your end. -- 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]
