<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] 22 new JSC test failures on the GTK+ ARM buildbot after r195233."
href="https://bugs.webkit.org/show_bug.cgi?id=153713#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] 22 new JSC test failures on the GTK+ ARM buildbot after r195233."
href="https://bugs.webkit.org/show_bug.cgi?id=153713">bug 153713</a>
from <span class="vcard"><a class="email" href="mailto:ossy@webkit.org" title="Csaba Osztrogonác <ossy@webkit.org>"> <span class="fn">Csaba Osztrogonác</span></a>
</span></b>
<pre>JSCTEST_timeout is 60 seconds by default (set by run-javascriptcore-tests)
and is doubled by run-jsc-stress-tests if FTL JIT is enabled and
then multiplied with sqrt(number_of_processors).
r194601 disabled timeout accidentally, I only enabled it again in r195233.
Maybe your hardware needs more timeout than the default. Could you try
if setting bigger timeout via JSCTEST_timeout env fixes this issue?
"Illegal instruction
ERROR: Unexpected exit code: 132"
We should see "Timed out after xx.xxxxxxx seconds!" message too
(dumped by jsc.cpp), but it seems it is disabled on your bot.</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>