smengcl opened a new pull request, #11806:
URL: https://github.com/apache/ozone/pull/11806

   Generated-by: Claude Code (Opus 5.5)
   
   ## What changes were proposed in this pull request?
   
   `acceptance (ranger)` failed on master twice when the Apache mirror 
redirector (`closer.lua`) returned HTTP 503 for the Ranger Ozone plugin 
tarball. `download_if_not_exists` in `compose/testlib.sh` runs `curl` without 
retries, so the file was missing and `test-ranger.sh` failed at `tar` before 
the cluster started. The same URL downloaded fine seconds later for 
`test-sts.sh` in the same job.
   
   This adds `--retry 3` to that `curl` call, so transient HTTP errors (408, 
429, 5xx) and timeouts are retried with exponential backoff (1s, 2s, 4s). All 
callers of `download_and_verify_apache_release` benefit.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-17510
   
   ## How was this patch tested?
   
   - In an `ubuntu:24.04` container (same curl as the GitHub runners), `curl 
--fail --location --output /tmp/x --retry 3 --show-error --silent 
https://httpbin.org/status/503` makes 4 attempts over about 7.5s before failing 
with exit code 22. Without `--retry` it fails on the first 503.
   - `bats` checks: all 92 test cases pass (`compose_testlib.bats` fails to 
load on the local macOS bats setup, the same on master).
   - The 10x10 flaky-test-check workflow only runs Java test classes, so it 
does not apply here. CI on this branch: 
[build-branch](https://github.com/smengcl/hadoop-ozone/actions/runs/40585786678),
 in progress.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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]

Reply via email to