-
Bug
-
Resolution: Duplicate
-
P4
-
None
-
9
Several runtime/CommandLine fails with fastdebug bundles, because processing of some options may be different comparing to product bundles.
Following tests are affected:
a) runtime/CommandLine/CompilerConfigFileWarning.java
runtime/CommandLine/ConfigFileWarning.java
Root cause: fastdebug JVM uses default compiler config and hotspot config files when appropriate CLI options are omitted.
b) runtime/CommandLine/VMOptionWarning.java
Root cause: UnlockUnreognizedVMOptions is true in debug, but test based on assumption that usage of diagnostic option w/o UnlockUnreognizedVMOptions will cause startup failure.
These tests should be updated to work correctly with both product and fastdebug builds.
Root cause:
Following tests are affected:
a) runtime/CommandLine/CompilerConfigFileWarning.java
runtime/CommandLine/ConfigFileWarning.java
Root cause: fastdebug JVM uses default compiler config and hotspot config files when appropriate CLI options are omitted.
b) runtime/CommandLine/VMOptionWarning.java
Root cause: UnlockUnreognizedVMOptions is true in debug, but test based on assumption that usage of diagnostic option w/o UnlockUnreognizedVMOptions will cause startup failure.
These tests should be updated to work correctly with both product and fastdebug builds.
Root cause:
- duplicates
-
JDK-8053889 com/oracle/java/testlibrary/Platform::isDebugBuild may return false when build is actually debug
-
- Closed
-