fallintoplace opened a new issue, #1535: URL: https://github.com/apache/iceberg-go/issues/1535
Two integration jobs failed during setup because Docker Hub timed out while pulling images: - https://github.com/apache/iceberg-go/actions/runs/30167050157/job/89701755026 - https://github.com/apache/iceberg-go/actions/runs/30167050070/job/89701754817 Both failed before tests ran with a request timeout against registry-1.docker.io. Their Spark 4 counterparts completed successfully. The current integration setup uses a single docker compose up -d --wait, so a transient registry failure fails the entire job. Possible solutions: 1. In CI, retry docker compose pull with backoff, then run docker compose up -d --wait --pull never. 2. Retry the complete integration setup command. This is simpler but may recreate a partially started environment. 3. Limit concurrent image pulls and add retry/backoff to reduce registry pressure. 4. Use a registry mirror or preloaded image cache if the project has suitable infrastructure. I lean toward option 1 because it keeps retry handling in CI and does not change local development behavior. Would maintainers prefer that approach, or a reusable retry target in the Makefile? Happy to implement the preferred solution. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
