-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-28701][test-hadoop3.2][test-java11][k8s] adding java11 support for pull request builds #25423
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
Closed
Closed
[SPARK-28701][test-hadoop3.2][test-java11][k8s] adding java11 support for pull request builds #25423
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
69e77e2
adding java11 support for pull request builds
shaneknapp e608ada
remove debugging, lower-case the title of the PRB
shaneknapp 1cc6bcb
added support for java version flag
shaneknapp 88014ed
added default java version for testing (8)
shaneknapp f285b70
add java bin to PATH
shaneknapp 3ce96e1
add java-version to SBT opts
shaneknapp 9670bbf
comment out changes, test java11 via prb config only
shaneknapp 7689b95
style ftw
shaneknapp c4ddeff
moving java11 setup from run-test-jenkins.py to run-tests.py
shaneknapp 4d99b96
skip unidoc building for now
shaneknapp bae6524
uncomment unidoc build as it runs under java8
shaneknapp File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Can we try to set this in python tests too? Seems like Java gateway has to use JDK 11 as well.
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.
It should use Java 11 if the path provides Java 11 and the test harness that runs Python tests does too. At least I don't know how else one would tell pyspark what to use!
In fact I'm pretty sure the test failure here shows that it is using JDK 11. From JPMML:
java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactoryThis would be caused by JDK 11 changes. However, I don't get why all the other non-Python tests don't fail.Given the weird problem in #24651 I am wondering if we have some subtle classpath issues with how the Pyspark tests are run.
This one however might be more directly solvable by figuring out what is suggesting to use this old Sun JAXB implementation. I'll start digging around META-INF
Uh oh!
There was an error while loading. Please reload this page.
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.
Hm, and why does https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test%20(Dashboard)/job/spark-master-test-maven-hadoop-3.2-jdk-11/ pass then? it is doing the same thing in the Jenkins config. (OK I think I answered my own question below)
EDIT: Oh, because it doesn't run Pyspark tests?
Uh oh!
There was an error while loading. Please reload this page.
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.
No, actually you're right. Yes, seems after Scala tests here, the PATH and JAVA_HOME still set as are.
I thought:
spark/python/pyspark/java_gateway.py
Lines 45 to 60 in 209b936
spark/core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala
Line 425 in 3cb8204
Here somehow happened to use JDK 8.
Actually the PySpark tests and SparkR tests passed at #25443 (comment)
So, the issue persists here .. but I guess yes we can do it separately since at least this PR seems setting JDK 11 correctly, and it virtually doesn't affect any main or test code (if this title is not used).
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.
It's interesting. Thank you for the investigation, @srowen and @HyukjinKwon
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.
Do we have a JIRA issue for this?
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.
We probably need one, yeah, regardless of the cause. I'll file one to track.
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.
https://issues.apache.org/jira/browse/SPARK-28877