-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
[test] Java 17 upgrade w/ Java 8 bytecode #23803
base: master
Are you sure you want to change the base?
Conversation
a8d965a
to
227f154
Compare
Collating the test failures I see so far -
|
I looked into presto-accumuloThis one failed because the product-tests-specific-environment2This one failed because it looks like tests-other-modulesSeems mostly add-opens issues. Needs:
|
product-tests-specific-environment2I believe these failures happen since we are building with Java 17 but using Java 8 at runtime in the docker images. These issues should likely be fixed once the docker images are updated to use Java 17. We should also look into enhancing Tempto to be able to use multiple Java versions so that we can run our CI pipeline with both Java 8 and Java 17+ and pass an argument to be able to choose which Java version to use while starting the Presto server in the docker images. |
test-other-modulesApart from the add-opens issues, I see issues while trying to connect to the zookeeper client in presto-kafka due to which none of the tests ran. Most likely the version is not compatible with Java 17.
|
test (:presto-spark-base -P presto-spark-tests-smoke)Current failures are all related to add-opens issues. But many tests were skipped due to these, we will have a better idea once we fix them. test (:presto-spark-base -P presto-spark-tests-all-queries)Current failures are all related to add-opens issues. But all tests were skipped due to these, we will have a better idea once we fix them. test / test (:presto-spark-base -P presto-spark-tests-spill-queries)Current failures are all related to add-opens issues. But all tests were skipped due to these, we will have a better idea once we fix them. |
3654a49
to
b6cab24
Compare
6b1917b
to
e6b7f1d
Compare
|
3893f06
to
72da587
Compare
There are a large number of parameters passed to argLine through the airbase POM. Set the airbase-specific props instead to aid in test failures
It seems later JVMs have drasitically improved their String representations. However, the string test is a bit of a wash because the estimated size entirely depends upon the strings which are used as input to the sketch. I think it's ok for this test to not be accurate for string-typed arguments for now.
CI actions seem to fail due to this line: https://github.com/apache/spark/blob/866816eb97002863ec205d854e1397982aecbc5e/core/src/main/scala/org/apache/spark/serializer/SerializationDebugger.scala#L70-L71 Attempting to access an item from sun.security.action
For future, we can leave this as the default (true), but for testing on the PR we want to see both actions run
to one that uses JDK 17
Temp change to limit the errors from using a JDK 17 only image
642c536
to
9ec6776
Compare
bbbf26d
to
309e0d7
Compare
309e0d7
to
bc0dbe6
Compare
repository tag copied from the maven 3 super POM at https://maven.apache.org/ref/3.9.9/maven-model-builder/super-pom.html
- Uses new image 'aaneja/hdp2.6-hive-kerberized-jdk17' that is the base `hdp2.6-hive-kerberized` with JDK 17 added to `/opt/java` - presto-launcher-wrapper.sh was updated to use Java from `/opt/java` if present - New add-opens for Keberos classes
5a87598
to
bbdbb16
Compare
- multinode-tls-kerberos updated to use `aaneja/hdp2.6-hive-kerberized-jdk17` - singlenode-ldap updated to use new image `aaneja/centos6-oj8-openldap-jdk17` - product-tests-specific-environment2 updated to only run on JDK 17 for now
5643924
to
18d435a
Compare
Description
Motivation and Context
Impact
Test Plan
Contributor checklist
Release Notes
Please follow release notes guidelines and fill in the release notes below.
If release note is NOT required, use: