RFR (S): 8010913 : compiler/6863420 often exceeds timeout

Vladimir Kozlov vladimir.kozlov at oracle.com
Mon Apr 1 12:01:36 PDT 2013


Main loop should also check 'done':

for (int numThreads = 1; numThreads <= 32; numThreads++) {

Thanks,
Vladimir

On 3/28/13 10:45 AM, David Chase wrote:
> Problem:
> The test runs over-long on some test machines, causing timeouts and spurious failures
> if JPRT is used to check compiler tests across a range of machines.
> A four-minute run was observed in one case.
>
> Fix:
> Add an increased timeout and a timeout thread for shutting down the test early.
>
> Testing:
> JPRT of that test across all available platforms with an artificially short timeout
> to ensure that the timeout thread worked as expected, manual check of successful
> runs to be sure that the timeout thread did its job (i.e., saw runs for a hair more than
> the time limit, as well as short runs).
>
> webrev:
> http://cr.openjdk.java.net/~drchase/8010913/webrev.00/
>


More information about the hotspot-compiler-dev mailing list