<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<body bgcolor="#FFFFFF" text="#000000">
I'm investigating the current jdk tests with timeouts to see if we <br>
can make them more reliable for slower machines. As a a first step,<br>
I want to see if the jtreg command line arguments can be made <br>
visible to the individual test.<br>
Second I want to explore the information about the target machine
can help adjust time limits from the time sensitive tests.<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject: </th>
<td>Re: Passing time factor to tests run under jtreg</td>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Tue, 15 Nov 2011 22:45:03 +0000</td>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>Alan Bateman <a class="moz-txt-link-rfc2396E" href="mailto:Alan.Bateman@oracle.com"><Alan.Bateman@oracle.com></a></td>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td>gary Adams <a class="moz-txt-link-rfc2396E" href="mailto:Gary.Adams@Oracle.COM"><Gary.Adams@Oracle.COM></a></td>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:email@example.com">firstname.lastname@example.org</a></td>
<pre>Gary - this might be something to bring up on the jtreg-use list.
Ideally the tests wouldn't have any hardcoded timeouts but sometimes
there isn't any other choice.
On 15/11/2011 20:14, Gary Adams wrote:
> I've been scanning a number of the slow machine test
> bugs that are reported and wanted to check to see if
> anyone has looked into time dependencies in the regression
> tests previously. From what I've been able to learn so far
> individual bugs can use the "timeout" parameter to indicate to
> the test harness an expected time to run.
> The test harness has command line arguments where it can
> filter out tests that take too long (timelimit) or can apply a
> multiplier to
> to the timeout when conditions are known to slow down the process
> (timeoutFactor). e.g. 8X for a slow machine or running with -Xcomp
> I see that there are some wrappers that can be applied around running
> a particular test to allow processing before main(). Could this mechanism
> be exploited so the harness command line options could be made known
> to the time dependent tests as command line arguments or as system
> My thought is the current timeout granularity is too large and only
> to the full test execution. If a test knew that a timeoutFactor was to
> be applied,
> it could internally adjust the time dependent delays appropriately. e.g.
> not every sleep(), await(), join() with timeouts would need the
> Before any test could be updated the information would need to be
> from the test context.
> Any feedback/pointers appreciated!