v8-raytrace JSC stress test failures

• Component: JavaScriptCore
• Status: NEW ---

[Ryan Haddad]

v8-raytrace JSC stress test failures

Run:
<https://build.webkit.org/builders/Apple%20Mavericks%2032-bit%20JSC%20%28BuildAndTest%29/builds/14146>
Result:
<https://build.webkit.org/builders/Apple%20Mavericks%2032-bit%20JSC%20%28BuildAndTest%29/builds/14146/steps/webkit-32bit-jsc-test/logs/stdio>

** The following JSC stress test failures have been introduced:
	regress/script-tests/v8-raytrace-with-empty-try-catch.js.always-trigger-copy-phase
	regress/script-tests/v8-raytrace-with-empty-try-catch.js.default
	regress/script-tests/v8-raytrace-with-empty-try-catch.js.default-ftl
	regress/script-tests/v8-raytrace-with-empty-try-catch.js.dfg-maximal-flush-validate-no-cjit
	regress/script-tests/v8-raytrace-with-empty-try-catch.js.no-cjit-validate-phases
	stress/v8-raytrace-strict.js.dfg-maximal-flush-validate-no-cjit
	v8-v6/v8-raytrace.js.dfg-maximal-flush-validate-no-cjit

Started between r192416 and r192443, not yet sure of exact rev due to jsc test being broken until r192443.

[Saam Barati]

Maybe this:
http://trac.webkit.org/changeset/192439
I'll look into it.

[Alexey Proskuryakov]

Rolling out r192401 fixed this, even though that's not when it started. Keeping this open since it's a mystery.

> not yet sure of exact rev due to jsc test being broken until r192443.

We should roll out more eagerly, even if asked to wait for a fix.