<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Testharness-based tests that timeout should be able to produce a detailled output"
href="https://bugs.webkit.org/show_bug.cgi?id=145313">145313</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Testharness-based tests that timeout should be able to produce a detailled output
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>528+ (Nightly build)
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>OS</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>Tools / Tests
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>youennf@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>Currently, the timeout for testharness based tests is set very high so that WebKit timeout always kicks in first.
This prevents testharness to produce meaningful reports, as in a single file, one test may timeout but not the others.
testharness should be able to report which tests are timeouting and which tests are not.
A first approach would be to put testharness timeout as the minimum value of all bots timeout.
One potential issue is that WebKit timeout depends on bot options (Mac, GTK, Debug, Release, Guard Malloc...), while testharness timeouts only depend on the document.
If the first approach does not work, the infrastructure may be upgraded to set the testharness.js timeout value dynamically at the beginning of the test process.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>