RFR(XXS): 8209566: [TESTBUG] runtime/appcds/jigsaw/modulepath/JvmtiAddPath.java timeout on tier6 on sparc (original) (raw)

Calvin Cheung calvin.cheung at oracle.com
Mon Oct 29 17:30:30 UTC 2018

Thanks for your quick review, Dan.

Calvin

On 10/29/18, 9:48 AM, Daniel D. Daugherty wrote:

Thumbs up! (and trivial)

Dan

On 10/29/18 12:43 PM, Calvin Cheung wrote: bug: https://bugs.openjdk.java.net/browse/JDK-8209566

The fix for JDK-8212028 decreased the timeout factor from 10 to 4. This test has been timing out occasionally in tier6 testing. The timeout could be reproduced by running the test on a solaris/sparc host many times. After increasing the timeout to 240, the timeout was not seen. Before the timeout factor change, the effective timeout is: 120s (default) x 10 = 1200s. With this change, the effective timeout is: 240s x 4 = 960s. Below is the diff: bash-4.2$ hg diff test/hotspot/jtreg/runtime/appcds/jigsaw/modulepath/JvmtiAddPath.java diff --git a/test/hotspot/jtreg/runtime/appcds/jigsaw/modulepath/JvmtiAddPath.java b/test/hotspot/jtreg/runtime/appcds/jigsaw/modulepath/JvmtiAddPath.java --- a/test/hotspot/jtreg/runtime/appcds/jigsaw/modulepath/JvmtiAddPath.java +++ b/test/hotspot/jtreg/runtime/appcds/jigsaw/modulepath/JvmtiAddPath.java @@ -33,7 +33,7 @@ * @build sun.hotspot.WhiteBox * @run driver ClassFileInstaller sun.hotspot.WhiteBox * @compile ../../test-classes/JvmtiApp.java - * @run driver JvmtiAddPath + * @run driver/timeout=240 JvmtiAddPath */ Testing: Ran the test repeatedly on a solaris/sparc host with tier6 vm options. thanks, Calvin

More information about the hotspot-runtime-dev mailing list