[SPARK-50187][INFRA] Use latest Python dependencies for the build of Python client 3.5 <> 4.0 server #48719
Conversation
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
zhengruifeng approved these changes Oct 31, 2024
Member Author
| Merged to master. |
Member Author
| I will monitor and followup the build. |
Member
dongjoon-hyun left a comment
dongjoon-hyun left a comment There was a problem hiding this comment.
+1, LGTM.
Thank you so much, @HyukjinKwon and @zhengruifeng .
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?
This PR proposes to use the same latest Python dependencies in Python client 3.5 <> 4.0 server build. This is a sort of a followup of #48524.
Why are the changes needed?
https://github.com/apache/spark/actions/runs/11543780375/job/32128570166 fails apparently because of different grpc versions. While it is a legitimate failure to fix, that CI does not target to test all different dependency versions. It only targets 3.5cleint <> 4.0server. We should better make the test on its purpose.
Does this PR introduce any user-facing change?
No, dev-only.
How was this patch tested?
Will monitor the jobs
Was this patch authored or co-authored using generative AI tooling?
No.