[13] RFR(xs) 8227646: [TESTBUG] appcds/SharedArchiveConsistency timed out

Daniel D. Daugherty daniel.daugherty at oracle.com
Tue Jul 16 12:56:06 UTC 2019

On 7/16/19 12:31 AM, Calvin Cheung wrote:
> bug: https://bugs.openjdk.java.net/browse/JDK-8227646
> webrev: http://cr.openjdk.java.net/~ccheung/8227646/webrev.00/

     Does the test intentionally crash in one or more of the test cases?
     If not, then '-XX:-CreateCoredumpOnCrash' is not really needed.
     I don't think '-XX:-CreateCoredumpOnCrash' will prevent the timeout
     handling mechanism from trying to capture a core file in the case
     of a timeout.

     The test currently timed out with a default total timeout value of
     480 seconds; that 480 comes from the default timeout value of 120
     seconds and the default timeout factor of 4 (480 == 120 * 4).

     The 'timeout=1000' value will get you a total timeout value of 4000.
     I suspect that is not what you want.

     If you specify 'timeout=240', you'll get a total timeout value of
     960 seconds (240 * 4).


> Increase the timeout to 1000s and add the -XX:-CreateCoredumpOnCrash 
> option to disable coredump.
> Testing: on 2 macosx hosts on which the timeout was observed.
> thanks,
> Calvin

More information about the hotspot-runtime-dev mailing list