HyukjinKwon opened a new pull request, #57111: URL: https://github.com/apache/spark/pull/57111
### What changes were proposed in this pull request? Docker-backed JDBC integration suites (e.g. `PostgresKrbIntegrationSuite`) pull their Docker image in `beforeAll` with a single attempt. A transient registry/proxy error (observed on GitHub Actions: `HTTP 502 Bad Gateway`) or a one-off pull timeout aborts the entire suite even though the rest of the run had zero test failures. This wraps the image pull in a bounded retry loop (`spark.test.docker.imagePullAttempts`, default `3`) with linear backoff, so a transient failure no longer aborts the suite. The final failure is rethrown once all attempts are exhausted. ### Why are the changes needed? A single transient registry hiccup should not abort a whole Docker integration suite that otherwise passes. This was seen aborting the scheduled `build_java17` workflow on `branch-4.1` (`PostgresKrbIntegrationSuite` aborted in `beforeAll` on a 502). Targeting `master` so it can be backported to the maintenance branches where the flake was observed. ### Does this PR introduce _any_ user-facing change? No. Test-infrastructure change only. ### How was this patch tested? Fork CI (`build_java17`, `Run Docker integration tests`): ✅ **PASS** — https://github.com/HyukjinKwon/spark/actions/runs/28906195126 `Run completed ... Tests: succeeded 606, failed 0, canceled 0, ignored 151` — "All tests passed", with `PostgresKrbIntegrationSuite` (the suite that had aborted on the 502) running clean. (Verification ran on `branch-4.1`; the changed pull block is identical on `master`.) JIRA: https://issues.apache.org/jira/browse/SPARK-58028 -- 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]
