-
Bug
-
Resolution: Cannot Reproduce
-
P4
-
9
If run with
-XX:+UsePerfData -d64 -server -Xcomp -XX:MaxRAMFraction=8 -XX:+CreateCoredumpOnCrash -ea -esa -XX:-TieredCompilation -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -XX:+IgnoreUnrecognizedVMOptions -XX:+AggressiveOpts -XX:+IgnoreUnrecognizedVMOptions -XX:-UseCompressedOops
the hotspot test serviceability/tmtools/jstat/GcCauseTest01.java can time out after 1'920 seconds on solaris_sparc.
I run the test 10 times with the same combination of flags and with the same binary on a solaris_sparc machine. The machine had approximately the same hardware configuration as used when the original failure appeared. The test typically takes 90 seconds to execute.
Therefore, I suspect this problem to be related to the execution environment. Maybe filing this issue against qe-test/hotspot is not the best thing to do, so please reassign if appropriate.
-XX:+UsePerfData -d64 -server -Xcomp -XX:MaxRAMFraction=8 -XX:+CreateCoredumpOnCrash -ea -esa -XX:-TieredCompilation -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -XX:+IgnoreUnrecognizedVMOptions -XX:+AggressiveOpts -XX:+IgnoreUnrecognizedVMOptions -XX:-UseCompressedOops
the hotspot test serviceability/tmtools/jstat/GcCauseTest01.java can time out after 1'920 seconds on solaris_sparc.
I run the test 10 times with the same combination of flags and with the same binary on a solaris_sparc machine. The machine had approximately the same hardware configuration as used when the original failure appeared. The test typically takes 90 seconds to execute.
Therefore, I suspect this problem to be related to the execution environment. Maybe filing this issue against qe-test/hotspot is not the best thing to do, so please reassign if appropriate.