They are failing after http://trac.webkit.org/changeset/146840. The fails are same on both of ports. * inspector/console/console-eval-syntax-error.html Diff: --- /ramdisk/qt-linux-32-release-NRWT/build/layout-test-results/inspector/console/console-eval-syntax-error-expected.txt +++ /ramdisk/qt-linux-32-release-NRWT/build/layout-test-results/inspector/console/console-eval-syntax-error-actual.txt @@ -1,5 +1,5 @@ Tests that evaluating an expression with a syntax error in the console won't crash the browser. Bug 61194. foo(). -SyntaxError: Expected an identifier but found '}' instead +SyntaxError: Unexpected EOF *inspector/debugger/debugger-pause-in-eval-script.html Diff: --- /ramdisk/qt-linux-32-release-NRWT/build/layout-test-results/inspector/debugger/debugger-pause-in-eval-script-expected.txt +++ /ramdisk/qt-linux-32-release-NRWT/build/layout-test-results/inspector/debugger/debugger-pause-in-eval-script-actual.txt @@ -4,7 +4,7 @@ Evaluated script in console. Script execution paused. Call stack: - 0) testFunction (:3) + 0) testFunction (:2) Script execution resumed. Debugger was disabled. * inspector/extensions/extensions-eval.html --- /ramdisk/qt-linux-32-release-NRWT/build/layout-test-results/inspector/extensions/extensions-eval-expected.txt +++ /ramdisk/qt-linux-32-release-NRWT/build/layout-test-results/inspector/extensions/extensions-eval-actual.txt @@ -5,7 +5,7 @@ RUNNING TEST: extension_testEvalConsoleAPI Evaluate: "function" (exception: undefined) RUNNING TEST: extension_testEvalDefinesGlobalSymbols -Evaluate: {"func":"function","variable":42} (exception: undefined) +Evaluate: {"func":"undefined","variable":42} (exception: undefined) RUNNING TEST: extension_testEvalOk Evaluate: {"str":"foo","num":42} (exception: undefined) RUNNING TEST: extension_testEvalStatement
These results just need added to the platform expectations. They are correct.
Thanks for your quick response. I will add new baseline to Qt.
Added platform specific expected files in: http://trac.webkit.org/changeset/146876
I'm against adding 3 same expected file (Mac/EFL/Qt) for one test. It seems it is JSC/V8 related problem. As far as I remember there was a consensus that in this case the platform independent result should be the JSC specific result and the V8 specific should be in platform-chromium. inspector/console/console-eval-syntax-error.html still have chromium specific result, and its platform independent result is unused now, so it should be updated for JSC platforms. inspector/debugger/debugger-pause-in-eval-script.html and inspector/extensions/extensions-eval.html don't have chromium specific expected file now.
Makes sense to me. JSC is in WebKit, V8 isn't.
Created attachment 195089 [details] proposed patch I uploaded a patch for the problem. Ossy thanks for your help. :)
Comment on attachment 195089 [details] proposed patch r=me, but let's see if the Mac and the Chromium EWS is happy before landing.
Comment on attachment 195089 [details] proposed patch EWS bots are green, let's land it.
Comment on attachment 195089 [details] proposed patch Clearing flags on attachment: 195089 Committed r147083: <http://trac.webkit.org/changeset/147083>
All reviewed patches have been landed. Closing bug.