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

   ### What changes were proposed in this pull request?
   
   This is a partial revert of #55914 (SPARK-56889) restricted to 
`dev/infra/Dockerfile`. It restores the file to its state at `0a0d31bea00~1` — 
switching the system Python used in the base CI image from `python3.11` back to 
`python3.10`. All other 20 files changed by #55914 are kept as-is.
   
   ### Why are the changes needed?
   
   The `Build / Cache base image` workflow has been failing on every branch 
since #55914 was merged (2026-05-16): 
https://github.com/apache/spark/actions/runs/26010261434/job/76449371588
   
   The failure aborts at the first `Build and push` step (the base 
`./dev/infra/` image), with:
   
   ```
   RUN add-apt-repository ppa:deadsnakes/ppa
     ...
     ModuleNotFoundError: No module named 'pyparsing'
   ERROR: process "/bin/sh -c add-apt-repository ppa:deadsnakes/ppa" did not 
complete successfully: exit code: 1
   ```
   
   This breaks the cache build for all downstream image jobs, since the base 
layer is shared. Restoring the previous Dockerfile is the smallest change that 
unblocks the cache workflow while a forward fix is investigated.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. CI-only change. PySpark itself is unaffected — only the system Python 
inside the test image.
   
   ### How was this patch tested?
   
   This PR re-runs `Build / Cache base image` against the restored Dockerfile.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (model: claude-opus-4-7)


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