Bug 165770
| Summary: | REGRESSION (r209710?): JSC Stress test stress/spread-calling.js.ftl-eager-no-cjit timing out | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ryan Haddad <ryanhaddad> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ap, fpizlo, saam, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Other | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Ryan Haddad
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 | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ryan Haddad
This is seen on the Yosemite Release JSC bot.
Ryan Haddad
The only JSC change in the failing run was https://trac.webkit.org/changeset/209710
Ryan Haddad
(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
(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
Just happened on the first run of Sierra Release tester too, FWIW.
Radar WebKit Bug Importer
<rdar://problem/29758371>
Alexey Proskuryakov
Does bug 166689 have a complete fix for this, or is there something else that needs to be done?
Saam Barati
(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
*** This bug has been marked as a duplicate of bug 166689 ***