run-perf-tests Speedometer fails with the following error message: Running Speedometer/Full.html (1 of 1) ERROR: CONSOLE MESSAGE: line 208: Miss the info bar? Run TodoMVC from a server to avoid a cross-origin error. FAILED Finished: 30.388546 s Either r190370 fixed an existing bug or introduced a new regression.
Created attachment 262280 [details] Screenshot of Mavericks perf bot builds list
The regression went away when we rolled out the patch so I'm pretty certain this is the culprit.
Committed r190535: <http://trac.webkit.org/changeset/190535>
Temporarily ignored this console message.
(In reply to comment #4) > Temporarily ignored this console message. I think it is paper overing this serious regression. Why is it good to measure the performace if the test is completely broken?
*** This bug has been marked as a duplicate of bug 149621 ***
(In reply to comment #5) > (In reply to comment #4) > > Temporarily ignored this console message. > > I think it is paper overing this serious regression. Why is it > good to measure the performace if the test is completely broken? I don't think this is a serious regression. Tail optimization does change the JS behavior, and the benchmark isn't failing on the browser. It's just that we have one extra console message when ran inside WRT.
(In reply to comment #7) > (In reply to comment #5) > > (In reply to comment #4) > > > Temporarily ignored this console message. > > > > I think it is paper overing this serious regression. Why is it > > good to measure the performace if the test is completely broken? > > I don't think this is a serious regression. Tail optimization does change > the JS behavior, and the benchmark isn't failing on the browser. It's just > that we have one extra console message when ran inside WRT. I don't know the internals of this test. But theoretically I don't think if a JS engine should change the behaviour of any JS script anytime.
Wait, this isn't a duplicate of 149621.
<rdar://problem/22995488>
<rdar://problem/22995494>
Oh, nvm. I misread it. *** This bug has been marked as a duplicate of bug 149621 ***
<rdar://problem/22995514>