hawk9821 commented on PR #9903: URL: https://github.com/apache/seatunnel/pull/9903#issuecomment-3344513723
> From the logs, it seems that some tests are able to pull the mysql image successfully, while others report a error for the same tag. I'm curious about what could cause this difference. Any insight would be appreciated! > > ``` > 2025-09-28T12:43:42.7145883Z [] 2025-09-28 12:43:42,714 INFO 🐳 [mysql:8.0] - Pulling image layers: 0 pending, 11 downloaded, 10 extracted, (224 MB/224 MB) > 2025-09-28T12:43:42.7364266Z [] 2025-09-28 12:43:42,736 INFO 🐳 [mysql:8.0] - Pulling image layers: 0 pending, 11 downloaded, 11 extracted, (224 MB/224 MB) > 2025-09-28T12:43:42.7438145Z [] 2025-09-28 12:43:42,743 INFO 🐳 [mysql:8.0] - Pull complete. 11 layers, pulled in 11s (downloaded 224 MB at 20 MB/s) > 2025-09-28T12:43:42.7459226Z [] 2025-09-28 12:43:42,745 INFO 🐳 [mysql:8.0] - Creating container for image: mysql:8.0 > 2025-09-28T12:43:42.7699914Z [] 2025-09-28 12:43:42,769 INFO 🐳 [mysql:8.0] - Container mysql:8.0 is starting: > ``` I've retried 4 times, but the error still occurs, is GitHub Actions unstable? ``` [ERROR] Plugin org.codehaus.mojo:versions-maven-plugin:2.16.0 or one of its dependencies could not be resolved: [ERROR] The following artifacts could not be resolved: org.codehaus.mojo:versions-maven-plugin:pom:2.16.0 (absent): org.codehaus.mojo:ve rsions-maven-plugin:pom:2.16.0 failed to transfer from https://repo.maven.apache.org/maven2 during a previous attempt. This failure was cached i n the local repository and resolution is not reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.codehaus.mojo:versions-maven-plugin:pom:2.16.0 from/to central (https://repo.maven.apache.org/maven2): Connect to [repo.maven.apache.org:443](https://repo.maven.apache.org/) [[repo.maven.apache.org/151.101.108.215](https://repo.maven.apache.org/151.101.108.215)] failed: connect timed out ``` -- 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]
