NEW 177254
[JSC] stress/function-constructor-semantics.js.ftl-eager-no-cjit is failing on Release JSC testers 
https://bugs.webkit.org/show_bug.cgi?id=177254
Summary [JSC] stress/function-constructor-semantics.js.ftl-eager-no-cjit is failing o...
Matt Lewis
Reported 2017-09-20 11:25:36 PDT
stress/function-constructor-semantics.js.ftl-eager-no-cjit is failing on Release JSC testers: first failure: https://build.webkit.org/builders/Apple%20Sierra%20Release%20JSC%20%28Tests%29/builds/3890 https://build.webkit.org/builders/Apple%20Sierra%20Release%20JSC%20%28Tests%29/builds/3890/steps/jscore-test/logs/stdio Error: Running stress/function-constructor-semantics.js.ftl-no-cjit-no-put-stack-validate stress/function-constructor-semantics.js.ftl-eager-no-cjit: test_script_10762: line 2: 40222 Segmentation fault: 11 ( "$@" ../../.vm/JavaScriptCore.framework/Resources/jsc --useFTLJIT\=false --useFunctionDotArguments\=true --maxPerThreadStackUsage\=1572864 --validateGraph\=true --airForceIRCAllocator\=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 function-constructor-semantics.js ) stress/function-constructor-semantics.js.ftl-eager-no-cjit: ERROR: Unexpected exit code: 139 FAIL: stress/function-constructor-semantics.js.ftl-eager-no-cjit According to the archive page, It started to fail after this revision https://trac.webkit.org/changeset/222263/webkit https://build.webkit.org/builders/Apple%20Sierra%20Release%20JSC%20%28Tests%29?numbuilds=200
Attachments
Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2017-09-20 17:17:23 PDT
> According to the archive page, It started to fail after this revision https://trac.webkit.org/changeset/222263/webkit This doesn't seem right - r222264 passed. So it just appears to be flaky. Matt, could you please attach a crash log from the bot?
Note You need to log in before you can comment on or make changes to this bug.