gaogaotiantian opened a new pull request, #56911:
URL: https://github.com/apache/spark/pull/56911

   ### What changes were proposed in this pull request?
   
   Install `zstd` in the CI container image Dockerfiles that are actually built 
by the `branch-4.1` scheduler (`branch41_scheduler.yml`): 
`dev/infra/Dockerfile` and the `docs`, `lint`, `sparkr`, `python-311`, 
`python-314`, and `pypy-310` images under `dev/spark-test-image/`.
   
   ### Why are the changes needed?
   
   On `branch-4.1`, `build_and_test.yml` extracts the precompiled artifact with 
`zstd -dc compile-artifact.tar.zst | tar -xf -`, but the container images do 
not have `zstd` installed, so the step fails with `zstd: not found`. (The same 
gap also defeats `actions/cache`, whose cache version embeds the compression 
method; container images without `zstd` fall back to `gzip` and never restore 
caches saved by host jobs.)
   
   This is the `branch-4.1`-scoped counterpart of SPARK-57278, which fixed the 
same problem on `master`. Only the images that the `branch-4.1` scheduler 
builds are modified here; the other Dockerfiles under `dev/spark-test-image/` 
are not used by any `branch-4.1` workflow.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. CI-only.
   
   ### How was this patch tested?
   
   CI on `branch-4.1`. The `Extract precompiled artifact` step now finds `zstd` 
in the rebuilt images, and `actions/cache` restores the Coursier cache in the 
container jobs.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (claude-opus-4-8)


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