[SPARK-56710][INFRA] branch-4.x and branch-4.2 scheduled CI, snapshots, and build_and_test Python split#55662
Closed
HyukjinKwon wants to merge 1 commit into
Closed
[SPARK-56710][INFRA] branch-4.x and branch-4.2 scheduled CI, snapshots, and build_and_test Python split#55662HyukjinKwon wants to merge 1 commit into
HyukjinKwon wants to merge 1 commit into
Conversation
HyukjinKwon
requested review from
LuciferYang,
dongjoon-hyun,
huaxingao and
zhengruifeng
and removed request for
LuciferYang and
dongjoon-hyun
HyukjinKwon
force-pushed
the
SPARK-56710
branch
3 times, most recently
from
3fa6323 to
3930e48
Compare
gengliangwang
approved these changes
May 4, 2026
Member
Author
|
Will merge and see how things go |
Member
Author
|
Merged to master. |
| # under the License. | ||
| # | ||
|
|
||
| name: "Build / Python-only (branch-4.2, PyPy 3.10)" |
Member
There was a problem hiding this comment.
It seems that this was mistakenly because PyPy retired at Spark 4.2.0 officially.
| # under the License. | ||
| # | ||
|
|
||
| name: "Build / Python-only (branch-4.x, PyPy 3.10)" |
Member
There was a problem hiding this comment.
Ditto. We retired PyPy.
Member
|
I made a follow-up PR. |
Member
Author
|
thanks! |
dongjoon-hyun
added a commit
that referenced
this pull request
May 17, 2026
…3.10.yml` ### What changes were proposed in this pull request? This PR aims to remove PyPy from `branch-4.x` and `branch-4.2` CIs because we retired it at Apache Spark 4.2.0 already. - #54988 ### Why are the changes needed? These two CIs seem to be added later to follow `branch-4.1` style, but `branch-4.x` and `branch-4.2` should be consistent from `master` branch when it comes to `PyPy`. - #55662 We don't need this test coverage from Apache Spark 4.2+. This removal will save our test infra resources. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Manual review. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code Closes #55918 from dongjoon-hyun/SPARK-56710. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
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
3 participants
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?
Scheduled GitHub workflows for
branch-4.xandbranch-4.2, snapshot matrix + README badges,build_and_testfor (branch-4.2/branch-4.xvsbranch-4.1), smallmerge_spark_pr.pyupdates.Why are the changes needed?
Spark 4 cut new integration/maintenance branches; CI and snapshots should track them without hand-editing workflow inputs.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually tested some logics. CI will be monitored separately.
Was this patch authored or co-authored using generative AI tooling?
No,