156163 2016-04-04 02:28:47 -0700 REGRESSION(r198989): It made 2 JSC stress tests fail on ARM Thumb2 2016-04-05 09:34:00 -0700 1 1 1 Unclassified WebKit JavaScriptCore Other Unspecified Unspecified RESOLVED DUPLICATE 155790 P2 Normal --- 108645 155672 1 ossy webkit-unassigned ggaren ossy saam ysuzuki oldest_to_newest 1180324 0 ossy 2016-04-04 02:28:47 -0700 https://trac.webkit.org/changeset/198989 made the jsc-layout-tests.yaml/js/script-tests/parser-syntax-check.js fail. And the new stress/sloppy-mode-function-hoisting.js fails since in it is introduced. https://build.webkit.org/builders/JSCOnly%20Linux%20ARMv7%20Thumb2%20Release/builds/145 (Note: These tests don't fail on the GTK ARM bot, but it's Thumb2, as far as I know.) Failing tests: jsc-layout-tests.yaml/js/script-tests/parser-syntax-check.js.layout jsc-layout-tests.yaml/js/script-tests/parser-syntax-check.js.layout-dfg-eager-no-cjit jsc-layout-tests.yaml/js/script-tests/parser-syntax-check.js.layout-no-cjit jsc-layout-tests.yaml/js/script-tests/parser-syntax-check.js.layout-no-llint stress/sloppy-mode-function-hoisting.js.always-trigger-copy-phase stress/sloppy-mode-function-hoisting.js.default stress/sloppy-mode-function-hoisting.js.dfg-eager stress/sloppy-mode-function-hoisting.js.dfg-eager-no-cjit-validate stress/sloppy-mode-function-hoisting.js.dfg-maximal-flush-validate-no-cjit stress/sloppy-mode-function-hoisting.js.no-cjit-validate-phases stress/sloppy-mode-function-hoisting.js.no-llint 1180457 1 saam 2016-04-04 13:14:26 -0700 Do you know why this is? It seems curious that a parser change would break something architecture related. 1180787 2 ysuzuki 2016-04-05 06:44:34 -0700 (In reply to comment #1) > Do you know why this is? > It seems curious that a parser change would break > something architecture related. Maybe, I guess this bot has some problem on dependency check. (We need to investigate it...) After performing the force-rebuild, this problem has gone away :) 1180825 3 saam 2016-04-05 09:09:05 -0700 (In reply to comment #2) > (In reply to comment #1) > > Do you know why this is? > > It seems curious that a parser change would break > > something architecture related. > > Maybe, I guess this bot has some problem on dependency check. (We need to > investigate it...) > After performing the force-rebuild, this problem has gone away :) Ok cool! Thanks. I'm closing this bug. 1180836 4 ossy 2016-04-05 09:34:00 -0700 Clean build didn't solve anything, but there are 600+ failures now. It seesm it is a dup of bug155790. *** This bug has been marked as a duplicate of bug 155790 ***