[SPARK-57708][INFRA] Install zstd in CI container images used by the branch-4.1 scheduler#56911
Open
gaogaotiantian wants to merge 1 commit into
Open
Conversation
…branch-4.1 scheduler ### 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) Co-authored-by: Isaac
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Install
zstdin the CI container image Dockerfiles that are actually built by thebranch-4.1scheduler (branch41_scheduler.yml):dev/infra/Dockerfileand thedocs,lint,sparkr,python-311,python-314, andpypy-310images underdev/spark-test-image/.Why are the changes needed?
On
branch-4.1,build_and_test.ymlextracts the precompiled artifact withzstd -dc compile-artifact.tar.zst | tar -xf -, but the container images do not havezstdinstalled, so the step fails withzstd: not found. (The same gap also defeatsactions/cache, whose cache version embeds the compression method; container images withoutzstdfall back togzipand never restore caches saved by host jobs.)This is the
branch-4.1-scoped counterpart of SPARK-57278, which fixed the same problem onmaster. Only the images that thebranch-4.1scheduler builds are modified here; the other Dockerfiles underdev/spark-test-image/are not used by anybranch-4.1workflow.Does this PR introduce any user-facing change?
No. CI-only.
How was this patch tested?
CI on
branch-4.1. TheExtract precompiled artifactstep now findszstdin the rebuilt images, andactions/cacherestores 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)