<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 - Debug test bots exit early frequently. Raise exit-after-n-crashes-or-timeouts to 100."
href="https://bugs.webkit.org/show_bug.cgi?id=153780">153780</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Debug test bots exit early frequently. Raise exit-after-n-crashes-or-timeouts to 100.
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>Other
</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>clopez@igalia.com
</td>
</tr>
<tr>
<th>CC</th>
<td>bugs-noreply@webkitgtk.org, cgarcia@igalia.com, lforschler@apple.com, mcatanzaro@igalia.com
</td>
</tr></table>
<p>
<div>
<pre>We are having the GTK+ debug test bot abort early frequently <a href="https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Debug%20%28Tests%29?numbuilds=200">https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Debug%20%28Tests%29?numbuilds=200</a>
Despite our best efforts to have it under control, there are still many tests timing out or asserting on the GTK+ debug bot.
The current threshold of 50 timeouts or crashes for abort early looks a bit tight to me.
The last time that this threshold was raised was 3 years ago on <a href="http://trac.webkit.org/changeset/150303">http://trac.webkit.org/changeset/150303</a> (it was raised from 20 to 50).
At that time, we had 34459 tests. Now (as of r195986) we have 44165 tests (28% more).
Currently, not only the GTK+ Debug bot is aborting early. Also 'Apple El Capitan Debug WK1' seems to abort early from time to time.
I see more value on the bot completing the test suite than aborting early. At least for me is more useful to see 85 crashes than to see an abort early because >50 crashes was reached.
So I propose to raise this to 100. I think is a reasonable trade-off.
Patch is coming.</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>