ChuckLin2025 commented on PR #57462: URL: https://github.com/apache/spark/pull/57462#issuecomment-5087744584
> Hi @cloud-fan @Ngone51 — a heads-up on the CI status on this PR. > > The failing checks are **all downstream of one infra failure**, not the code change. The `Base image build` job fails while building the PySpark test image with: > > ``` > ERROR: failed to solve: root: failed to resolve source metadata for > docker.io/library/root:latest: pull access denied ... insufficient_scope > ``` > > This cascades into every `pyspark-*` module (they fail at "Initialize containers" because the image was never built). It reproduces deterministically across three re-runs. > > I believe this is a **fork-runner / buildx environment issue, not a problem with this PR**: > > * The branch is at exactly current `master` and touches no `.github/` or `dev/spark-test-image/` files. > * `dev/spark-test-image/python-312/Dockerfile` is a clean single-stage `FROM ubuntu:noble` — there's no `root` stage in it; buildkit seems to synthesize a phantom `root:latest` stage during provenance attestation on my fork. > * apache/spark's own `master` CI builds the identical Dockerfile green. > > All the checks that actually exercise this change are passing: `core, unsafe, ... network-common ...` (the new `TransportClient`/`TransportClientFactory` tests), the config binding-policy audit, linters, and the rest of the JVM/SQL suites. > > Could you advise on how you'd like to proceed? A few options I see: > > 1. Treat the pyspark failures as unrelated infra and review on the JVM results (this PR has no Python surface). > 2. I re-run CI once a committer kicks it off on Apache infra, where the image build works. > 3. Any fork-side workaround you'd recommend (e.g. disabling provenance attestation) — happy to apply it if useful. > > Thanks! Thanks @Ngone51. Addressed by sync and retry. -- 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]
