JDK-8268267 : Remove -Djavatest.security.noSecurityManager=true from jtreg runs
- Type: Bug
- Component: security-libs
- Sub-Component: java.security
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-06-04
- Updated: 2021-06-11
- Resolved: 2021-06-07
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 17 |
|---|
17 b26Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
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.
Comments
|