[SPARK-58285][INFRA] Remove stale container CI dependency bypasses#57457
Closed
zhengruifeng wants to merge 1 commit into
Closed
[SPARK-58285][INFRA] Remove stale container CI dependency bypasses#57457zhengruifeng wants to merge 1 commit into
zhengruifeng wants to merge 1 commit into
Conversation
zhengruifeng
marked this pull request as ready for review
July 23, 2026 06:58
zhengruifeng
requested review from
HyukjinKwon,
dongjoon-hyun and
gaogaotiantian
July 23, 2026 06:58
zhengruifeng
marked this pull request as draft
July 23, 2026 07:10
zhengruifeng
marked this pull request as ready for review
July 23, 2026 07:12
zhengruifeng
marked this pull request as draft
July 23, 2026 07:16
zhengruifeng
marked this pull request as ready for review
July 23, 2026 07:28
zhengruifeng
force-pushed
the
remove-pyspark-needs-bypass-dev4
branch
from
July 23, 2026 07:44
09a9639 to
c050070
Compare
dongjoon-hyun
approved these changes
Jul 23, 2026
dongjoon-hyun
left a comment
Member
There was a problem hiding this comment.
+1 for the extended scope from PySpark to all cancelled CIs.
Is this all, @zhengruifeng ?
Contributor
Author
@dongjoon-hyun yes, i think so |
uros-b
approved these changes
Jul 23, 2026
Member
|
Thank you @zhengruifeng and @dongjoon-hyun! |
zhengruifeng
added a commit
that referenced
this pull request
Jul 23, 2026
### What changes were proposed in this pull request? Removes the cancelled-status dependency bypasses from the PySpark, SparkR, lint, and documentation jobs. Replaces the PySpark matrix's obsolete non-master fallback comments with descriptions of the entries selected by each change gate. ### Why are the changes needed? The bypasses were introduced when non-master jobs used static fallback container images. These jobs now use per-run images produced by infra-image. When that build fails, the bypass still schedules the entire PySpark matrix and the SparkR, lint, and documentation jobs; they then fail minutes later while trying to start from images that were never pushed. No dependent container job can run successfully in that state, so GitHub Actions should block them until infra-image succeeds. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Ran git diff --check. No test suite was run because this is a GitHub Actions job-condition and comment change. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Codex (GPT-5) Closes #57457 from zhengruifeng/remove-pyspark-needs-bypass-dev4. Authored-by: Ruifeng Zheng <ruifengz@apache.org> Signed-off-by: Ruifeng Zheng <ruifengz@apache.org> (cherry picked from commit 3ce5de6) Signed-off-by: Ruifeng Zheng <ruifengz@apache.org>
Contributor
Author
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
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?
Removes the cancelled-status dependency bypasses from the PySpark, SparkR, lint, and documentation jobs. Replaces the PySpark matrix's obsolete non-master fallback comments with descriptions of the entries selected by each change gate.
Why are the changes needed?
The bypasses were introduced when non-master jobs used static fallback container images. These jobs now use per-run images produced by infra-image. When that build fails, the bypass still schedules the entire PySpark matrix and the SparkR, lint, and documentation jobs; they then fail minutes later while trying to start from images that were never pushed. No dependent container job can run successfully in that state, so GitHub Actions should block them until infra-image succeeds.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Ran git diff --check. No test suite was run because this is a GitHub Actions job-condition and comment change.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Codex (GPT-5)