<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 - Slow JSC stress tests fail on 32 bit debug bots"
href="https://bugs.webkit.org/show_bug.cgi?id=154964">154964</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Slow JSC stress tests fail on 32 bit debug bots
</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>Critical
</td>
</tr>
<tr>
<th>Priority</th>
<td>P1
</td>
</tr>
<tr>
<th>Component</th>
<td>New Bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>ossy@webkit.org
</td>
</tr>
<tr>
<th>CC</th>
<td>ap@webkit.org, fpizlo@apple.com, rniwa@webkit.org
</td>
</tr>
<tr>
<th>Blocks</th>
<td>154858
</td>
</tr></table>
<p>
<div>
<pre><a href="http://trac.webkit.org/changeset/197442">http://trac.webkit.org/changeset/197442</a> disabled FTL JIT testing
on 32 bit bots, because there is no FTL JIT on any 32 bit platforms.
But 25-35 tests started to fail on these bots:
- <a href="https://build.webkit.org/builders/Apple%20El%20Capitan%2032-bit%20JSC%20%28BuildAndTest%29/builds/1658">https://build.webkit.org/builders/Apple%20El%20Capitan%2032-bit%20JSC%20%28BuildAndTest%29/builds/1658</a>
- <a href="https://build.webkit.org/builders/Apple%20Yosemite%2032-bit%20JSC%20%28BuildAndTest%29">https://build.webkit.org/builders/Apple%20Yosemite%2032-bit%20JSC%20%28BuildAndTest%29</a>
The problem is that these tests seems to be very slow in debug mode,
but they didn't fail previously because jsc-stress-tests script
duplicated the timeout in case of FTL JIT is enabled:
if $enableFTL and ENV["JSCTEST_timeout"]
# Currently, using the FTL is a performance regression particularly in real
# (i.e. non-loopy) benchmarks. Account for this in the timeout.
ENV["JSCTEST_timeout"] = (ENV["JSCTEST_timeout"].to_i * 2).to_s
end
It seems we should duplicate timeout in debug mode too.</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>