-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
More fixes about running tests on JDK11 #9893
More fixes about running tests on JDK11 #9893
Conversation
/pulsarbot run-failure-checks |
@merlimat I have addressed your comments PTAL |
### Motivation When you are running tests on JDK11 you encounter a lot of issues. This patch includes a list of minor fixes that can be grouped. Master issue apache#9578 ### Modifications - Upgrade Mockito to latest version - Add "--add-opens java.base/jdk.internal.loader=ALL-UNNAMED" in order to allow PowerMock to work - add JAXB into jcloud provider (we already have it on the classpath in production, it is only in order to let tests run) - Upgrade HDFS minicluster to 3.3.0 - Pin netty-codec-http dependency to the same version of netty (inherited from HDFS client) - Use the same version of Jetty for hdfs-offload (old version does not work with JDK11)
Hi, I just pull the latest master and when I ran a test with Intellij Idea, it failed to start with following error message
I think it may be caused by this PR. <profile>
<id>jdk11-tests</id>
<activation>
<jdk>[11,)</jdk>
</activation>
<properties>
<test.additional.args> --add-opens java.base/jdk.internal.loader=ALL-UNNAMED </test.additional.args>
</properties>
</profile> But even after I removed these lines from |
In IntelliJ check if it automatically enabled this profile. If so then simply unselect it. @BewareMyPower we can continue on slack |
Thanks for you advice. I found the real cause just now, which is not related to this profile. The error may be caused by some Maven plugins, see https://youtrack.jetbrains.com/issue/IDEA-258574 I just fixed it by disabling the |
When you are running tests on JDK11 you encounter a lot of issues. This patch includes a list of minor fixes that can be grouped. Master issue apache#9578 - Upgrade Mockito to latest version - Add "--add-opens java.base/jdk.internal.loader=ALL-UNNAMED" in order to allow PowerMock to work - add JAXB into jcloud provider (we already have it on the classpath in production, it is only in order to let tests run) - Upgrade HDFS minicluster to 3.3.0 - Pin netty-codec-http dependency to the same version of netty (inherited from HDFS client) - Use the same version of Jetty for hdfs-offload (old version does not work with JDK11)
When you are running tests on JDK11 you encounter a lot of issues. This patch includes a list of minor fixes that can be grouped. Master issue apache#9578 - Upgrade Mockito to latest version - Add "--add-opens java.base/jdk.internal.loader=ALL-UNNAMED" in order to allow PowerMock to work - add JAXB into jcloud provider (we already have it on the classpath in production, it is only in order to let tests run) - Upgrade HDFS minicluster to 3.3.0 - Pin netty-codec-http dependency to the same version of netty (inherited from HDFS client) - Use the same version of Jetty for hdfs-offload (old version does not work with JDK11)
### Motivation When you are running tests on JDK11 you encounter a lot of issues. This patch includes a list of minor fixes that can be grouped. Master issue apache#9578 ### Modifications - Upgrade Mockito to latest version - Add "--add-opens java.base/jdk.internal.loader=ALL-UNNAMED" in order to allow PowerMock to work - add JAXB into jcloud provider (we already have it on the classpath in production, it is only in order to let tests run) - Upgrade HDFS minicluster to 3.3.0 - Pin netty-codec-http dependency to the same version of netty (inherited from HDFS client) - Use the same version of Jetty for hdfs-offload (old version does not work with JDK11) cherry picked manually from c94d782
Motivation
When you are running tests on JDK11 you encounter a lot of issues.
This patch includes a list of minor fixes that can be grouped.
Master issue #9578
Modifications
Verifying this change
Tests must still run successfully on JDK8.
Once all tests are known to run on JDK11 we will switch CI tests runner to JDK11, this cannot be done in this PR.