-
Notifications
You must be signed in to change notification settings - Fork 9.1k
YARN-11779. Reset mockito version to 2.18.0 in hadoop-yarn-ui #7440
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
Conversation
* There was a change to upgrade Mockito to 4.11.0 in apache#6968. * This broke the build on Windows in the hadoop-yarn-ui module - apache#6968 (comment). * Thus, we need to revert back to the previous stable version (2.18.0) of mockito for hadoop-yarn-ui.
@muskan1012 I've attempted to fix the build failure by reverting the mockito version in the |
💔 -1 overall
This message was automatically generated. |
Verified that the necessary steps are passing on Windows - Yetus logs - archive.zip |
@GauthamBanasandra the CI result shows a lot of test failures, can you check if they are related. The previous ticket HADOOP-19243, mentioned JDK-17 as the use case, we should see if this doesn't break that. Is there a way to fix the compilation while staying on the same mockito version? cc. @slfan1989 / @steveloughran |
We indeed need to upgrade HADOOP-19243. I have conducted unit tests offline, and without this PR, some unit tests will fail on JDK17. The Mockito version 4.11.0 is not very recent. After upgrading to JUnit5, we should also update the Mockito version. From a personal perspective, I believe downgrading is not a good approach. https://mvnrepository.com/artifact/org.mockito/mockito-core. Can we solve this problem by upgrading the version of the
@GauthamBanasandra Can we try upgrading the version of the https://mvnrepository.com/artifact/ro.isdc.wro4j/wro4j-maven-plugin |
@ayushtkn the test failures that you're referring to are on Windows and are expected to fail. |
2.18.0 is too old, why select this version, the last is 5.15.x |
@zeekling I was just restoring the version back to what it was, prior to the failure. |
I've tried to fix this issue by upgrading wro4j to |
Abandoning this PR since this was fixed by #7457. |
Description of PR
How was this patch tested?
Verified by building locally on Windows 11.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?