LuciferYang opened a new pull request, #13012:
URL: https://github.com/apache/gluten/pull/13012

   ## What changes are proposed in this pull request?
   
   `install_minio` in `.github/workflows/util/install-spark-deps.sh` downloads 
the MinIO server and client from `dl.min.io`, and both URLs now return HTTP 410 
Gone: MinIO has taken its community binaries off that host. `-f` makes curl 
exit non-zero and `set -e` fails the step, so every job that calls 
`install_minio` (`tpc-test-ubuntu` and the celeborn / uniffle / OOM / 
random-kill jobs, all in `velox_backend_x86.yml`) fails at MinIO install 
regardless of the change under test.
   
   This pulls the pinned release assets from GitHub instead. `minio/minio`'s 
latest release ships no assets, so the server is pinned to the last release 
that still carries them:
   
   - server `RELEASE.2025-09-07T16-13-09Z`
   - client `RELEASE.2025-08-13T08-35-41Z`
   
   Same event that broke Paimon CI (apache/paimon#9780), different surface: 
Paimon pulls `minio/minio` as a Docker image through testcontainers and 
requalified it to `quay.io/minio/minio`, but Gluten runs `minio server` and 
`mc` as standalone binaries, so it is the binary endpoint rather than an image 
name that needs to change. `linux-amd64` is unchanged, matching the one x86 
workflow that uses these helpers.
   
   ## How was this patch tested?
   
   `bash -n` on the script. Both asset URLs were downloaded directly: the 
server asset is a valid 110 MB x86-64 ELF binary and the client asset serves 
anonymously. Full coverage is the CI run on this PR, which is where 
`install_minio` and `setup_minio` actually execute.
   
   ## Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude claude-opus-5
   
   Related issue: #13011
   


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