-
Bug
-
Resolution: Fixed
-
P4
-
9
-
b112
-
x86
-
windows
The tests fail with:
Error occurred during initialization of VM
GC triggered before VM initialization completed. Try increasing NewSize, current value 1331K.
];
stderr: []
exitValue = 1
java.lang.RuntimeException: Expected to get exit value of [0]
at jdk.test.lib.OutputAnalyzer.shouldHaveExitValue(OutputAnalyzer.java:366)
at TestShrinkAuxiliaryData.performTest(TestShrinkAuxiliaryData.java:107)
at TestShrinkAuxiliaryData.test(TestShrinkAuxiliaryData.java:94)
at TestShrinkAuxiliaryData00.main(TestShrinkAuxiliaryData00.java:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:520)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:92)
at java.lang.Thread.run(Thread.java:804)
Seems to be similar to JDK-8040935 where the problem was triggered by -XX:+AggressiveOpts which is also used in this case.
Error occurred during initialization of VM
GC triggered before VM initialization completed. Try increasing NewSize, current value 1331K.
];
stderr: []
exitValue = 1
java.lang.RuntimeException: Expected to get exit value of [0]
at jdk.test.lib.OutputAnalyzer.shouldHaveExitValue(OutputAnalyzer.java:366)
at TestShrinkAuxiliaryData.performTest(TestShrinkAuxiliaryData.java:107)
at TestShrinkAuxiliaryData.test(TestShrinkAuxiliaryData.java:94)
at TestShrinkAuxiliaryData00.main(TestShrinkAuxiliaryData00.java:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:520)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:92)
at java.lang.Thread.run(Thread.java:804)
Seems to be similar to JDK-8040935 where the problem was triggered by -XX:+AggressiveOpts which is also used in this case.