-
Notifications
You must be signed in to change notification settings - Fork 9.1k
YARN-11863. [JDK17] Remove JUnit4 NoExitSecurityManager. #7986
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
💔 -1 overall
This message was automatically generated. |
I observed a I wasn’t able to reproduce this issue locally (
To verify whether this is only triggered by that specific test case in CI, I plan to temporarily disable |
💔 -1 overall
This message was automatically generated. |
Confirmed that the Maven Surefire thread overflow issue is unrelated to TestAppManager. In the local environment, TestAppManager passes tests successfully; even when TestAppManager is disabled, the thread overflow still occurs in CI. |
💔 -1 overall
This message was automatically generated. |
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 @slfan1989
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
@steveloughran @zhtttylz Thanks for the review! |
Description of PR
JIRA: YARN-11863. [JDK17] Remove JUnit4 NoExitSecurityManager.
During the process of completely removing JUnit4 dependencies, we found that the NoExitSecurityManager class is still used in the project. To further reduce JUnit4 dependencies and maintain code cleanliness, it needs to be removed.
How was this patch tested?
Manual testing.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?