JSC Stress test stress/spread-calling.js.ftl-eager-no-cjit timing out
stress/spread-calling.js.ftl-eager-no-cjit: Timed out after 339.000000 sec seconds!
stress/spread-calling.js.ftl-eager-no-cjit: ERROR: Unexpected exit code: 133
This is seen on the Yosemite Release JSC bot.
The only JSC change in the failing run was https://trac.webkit.org/changeset/209710
(In reply to comment #1)
> This is seen on the Yosemite Release JSC bot.
One instance seen on El Capitan Release here, so perhaps this is a flaky timeout:
(In reply to comment #3)
> (In reply to comment #1)
> > This is seen on the Yosemite Release JSC bot.
> One instance seen on El Capitan Release here, so perhaps this is a flaky
I'm on it...
Just happened on the first run of Sierra Release tester too, FWIW.
Does bug 166689 have a complete fix for this, or is there something else that needs to be done?
(In reply to comment #7)
> Does bug 166689 have a complete fix for this, or is there something else
> that needs to be done?
I believe all that's needed is to make the test run for less time. So bug 166689 should be sufficient.
*** This bug has been marked as a duplicate of bug 166689 ***