-
Notifications
You must be signed in to change notification settings - Fork 28.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-33565][PYTHON][BUILD][3.0] Remove py38 spark3 #30509
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, LGTM.
BTW, @shaneknapp . |
right now, i have to finish porting everything, including the master node, to ubuntu20. then in a ~month, reinstall all the old ubuntu 16 workers. during this time we'll also get through the backlog of outstanding package reqs, as well as setting up a py38 environment. |
Got it. No problem~ |
Test build #131814 has finished for PR 30509 at commit
|
### What changes were proposed in this pull request? remove python 3.8 from python/run-tests.py and stop build breaks ### Why are the changes needed? the python tests are running against the bare-bones system install of python3, rather than an anaconda environment. ### Does this PR introduce _any_ user-facing change? no ### How was this patch tested? jenkins see also #30506 Closes #30509 from shaneknapp/remove-py38-spark3. Authored-by: shane knapp <incomplete@gmail.com> Signed-off-by: shane knapp <incomplete@gmail.com>
hmm, well this didn't get autoclosed for some reason. closing manually. it's merged in to 3.0... |
Build finished. |
1 similar comment
Build finished. |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
LGTM. Thanks for fixing this. |
What changes were proposed in this pull request?
remove python 3.8 from python/run-tests.py and stop build breaks
Why are the changes needed?
the python tests are running against the bare-bones system install of python3, rather than an anaconda environment.
Does this PR introduce any user-facing change?
no
How was this patch tested?
jenkins
see also #30506