RESOLVED DUPLICATE of bug 166689 165770
REGRESSION (r209710?): JSC Stress test stress/spread-calling.js.ftl-eager-no-cjit timing out
https://bugs.webkit.org/show_bug.cgi?id=165770
Summary REGRESSION (r209710?): JSC Stress test stress/spread-calling.js.ftl-eager-no-...
Ryan Haddad
Reported 2016-12-12 13:03:42 PST
JSC Stress test stress/spread-calling.js.ftl-eager-no-cjit timing out https://build.webkit.org/builders/Apple%20Yosemite%20Release%20JSC%20%28Tests%29/builds/16477 stress/spread-calling.js.ftl-eager-no-cjit: Timed out after 339.000000 sec seconds! stress/spread-calling.js.ftl-eager-no-cjit: test_script_16271: line 2: 61700 Trace/BPT trap: 5 ( "$@" ../../.vm/JavaScriptCore.framework/Resources/jsc --useFTLJIT\=false --useFunctionDotArguments\=true --maxPerThreadStackUsage\=1572864 --validateGraph\=true --useFTLJIT\=true --useConcurrentJIT\=false --thresholdForJITAfterWarmUp\=100 --scribbleFreeCells\=true --thresholdForJITAfterWarmUp\=10 --thresholdForJITSoon\=10 --thresholdForOptimizeAfterWarmUp\=20 --thresholdForOptimizeAfterLongWarmUp\=20 --thresholdForOptimizeSoon\=20 --thresholdForFTLOptimizeAfterWarmUp\=20 --thresholdForFTLOptimizeSoon\=20 --maximumEvalCacheableSourceLength\=150000 --useEagerCodeBlockJettisonTiming\=true --collectContinuously\=true --useGenerationalGC\=false spread-calling.js ) stress/spread-calling.js.ftl-eager-no-cjit: ERROR: Unexpected exit code: 133 FAIL: stress/spread-calling.js.ftl-eager-no-cjit
Attachments
Ryan Haddad
Comment 1 2016-12-12 13:04:49 PST
This is seen on the Yosemite Release JSC bot.
Ryan Haddad
Comment 2 2016-12-12 13:27:18 PST
The only JSC change in the failing run was https://trac.webkit.org/changeset/209710
Ryan Haddad
Comment 3 2016-12-12 13:28:22 PST
(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: https://build.webkit.org/builders/Apple%20El%20Capitan%20Release%20JSC%20(Tests)?numbuilds=50
Filip Pizlo
Comment 4 2016-12-12 14:42:49 PST
(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 > timeout: > > https://build.webkit.org/builders/ > Apple%20El%20Capitan%20Release%20JSC%20(Tests)?numbuilds=50 I'm on it...
Alexey Proskuryakov
Comment 5 2016-12-16 10:37:39 PST
Just happened on the first run of Sierra Release tester too, FWIW.
Radar WebKit Bug Importer
Comment 6 2016-12-20 12:30:16 PST
Alexey Proskuryakov
Comment 7 2017-01-04 12:56:25 PST
Does bug 166689 have a complete fix for this, or is there something else that needs to be done?
Saam Barati
Comment 8 2017-01-04 13:09:32 PST
(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.
Alexey Proskuryakov
Comment 9 2017-01-04 13:12:03 PST
*** This bug has been marked as a duplicate of bug 166689 ***
Note You need to log in before you can comment on or make changes to this bug.