Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
P4
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 17
-
Component/s: security-libs
-
Labels:None
-
Subcomponent:
-
Resolved In Build:b26
Description
In the early days of JEP 411 we made -Djava.security.manager=disallow by default the following change for jtreg runs in RunTests.gmk was made:
- $1_JTREG_BASIC_OPTIONS += -automatic -ignore:quiet
+ $1_JTREG_BASIC_OPTIONS += -automatic -ignore:quiet -Djavatest.security.noSecurityManager=true
Now that we are back to allow but the change above is still integrated.
We can revert the change above, and thus liberate 3 langtools tests from problem list.
- $1_JTREG_BASIC_OPTIONS += -automatic -ignore:quiet
+ $1_JTREG_BASIC_OPTIONS += -automatic -ignore:quiet -Djavatest.security.noSecurityManager=true
Now that we are back to allow but the change above is still integrated.
We can revert the change above, and thus liberate 3 langtools tests from problem list.
Attachments
Issue Links
- relates to
-
JDK-8265611 @compile/ref comparison fails when -Djavatest.security.noSecurityManager=true is set
-
- Closed
-
-
JDK-8265611 @compile/ref comparison fails when -Djavatest.security.noSecurityManager=true is set
-
- Closed
-
-
JDK-8266459 Implement JEP 411: Deprecate the Security Manager for Removal
-
- Resolved
-
-
JDK-8264713 JEP 411: Deprecate the Security Manager for Removal
-
- Closed
-
(1 links to)