SharedReadWriteSize, SharedReadOnlySize, SharedMiscDataSize and SharedMiscCodeSize have default sizes, such that when one of them is set to the MAX, then the VM will exit with error code 2. This registers as a failure in the current framework, but in fact needs to be accepted as success in the cases of these particular flags (ie. failure is defined by a crash that produces error log, not by VM exit with error code)
TestOptionsWithRanges allows flags to be opted out using:
allOptionsAsMap.remove("SharedReadWriteSize");
but it also needs a mechanism that defines allowable exit codes. For most flags that exit code would be implicitly set to 0, but for Shared* it would be 0,2. Perhaps something like:
allOptionsAsMap.setAllowedExitCodes("SharedReadWriteSize", 0, 2, ...);
If we had such enhancement, then we could still test the Shared* flags, which at the moment must be disabled.
TestOptionsWithRanges allows flags to be opted out using:
allOptionsAsMap.remove("SharedReadWriteSize");
but it also needs a mechanism that defines allowable exit codes. For most flags that exit code would be implicitly set to 0, but for Shared* it would be 0,2. Perhaps something like:
allOptionsAsMap.setAllowedExitCodes("SharedReadWriteSize", 0, 2, ...);
If we had such enhancement, then we could still test the Shared* flags, which at the moment must be disabled.
- relates to
-
JDK-8138983 Runtime: implement ranges for Shared*** flags
-
- Closed
-
-
JDK-8059557 JEP 245: Validate JVM Command-Line Flag Arguments
-
- Closed
-