Bug 61267

Summary: Update chromium expectations after removal of execScript from V8
Product: WebKit Reporter: Mads Ager <ager>
Component: New BugsAssignee: Mads Ager <ager>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue, dglazkov, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Archive of layout-test-results from ec2-cr-linux-02 none

Mads Ager
Reported 2011-05-23 02:15:05 PDT
Update chromium expectations after removal of execScript from V8
Attachments
Patch (1.45 KB, patch)
2011-05-23 02:15 PDT, Mads Ager 		no flags
DetailsFormatted DiffDiff
Archive of layout-test-results from ec2-cr-linux-02 (1.28 MB, application/zip)
2011-05-23 02:56 PDT, WebKit Review Bot 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Mads Ager
Comment 1 2011-05-23 02:15:41 PDT
Created attachment 94386 [details] Patch
WebKit Review Bot
Comment 2 2011-05-23 02:56:33 PDT
Comment on attachment 94386 [details] Patch Attachment 94386 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/8726341 New failing tests: fast/dom/prototype-inheritance.html
WebKit Review Bot
Comment 3 2011-05-23 02:56:38 PDT
Created attachment 94393 [details] Archive of layout-test-results from ec2-cr-linux-02 The attached test failures were seen while running run-webkit-tests on the chromium-ews. Bot: ec2-cr-linux-02 Port: Chromium Platform: Linux-2.6.35-28-virtual-x86_64-with-Ubuntu-10.10-maverick
Mads Ager
Comment 4 2011-05-23 03:40:23 PDT
This change relies on a V8 version later than 3.3.9. I had to revert i chromium, so we need to not land this before V8 has been rolled again. Thanks.
WebKit Commit Bot
Comment 5 2011-05-25 00:49:07 PDT
Comment on attachment 94386 [details] Patch Clearing flags on attachment: 94386 Committed r87279: <http://trac.webkit.org/changeset/87279>
WebKit Commit Bot
Comment 6 2011-05-25 00:49:15 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.