Bug 156163
| Summary: | REGRESSION(r198989): It made 2 JSC stress tests fail on ARM Thumb2 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Csaba Osztrogonác <ossy> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ggaren, ossy, saam, ysuzuki |
| Priority: | P2 | ||
| Version: | Other | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 108645, 155672 | ||
Csaba Osztrogonác
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Saam Barati
Do you know why this is?
It seems curious that a parser change would break
something architecture related.
Yusuke Suzuki
(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 :)
Saam Barati
(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.
Csaba Osztrogonác
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 ***