Bug 110523

Summary: REGRESSION(r143536): Causing a bunch of tests to fail on Windows, requires rebaselining (Requested by rfong on #webkit).
Product: WebKit Reporter: WebKit Review Bot <webkit.review.bot>
Component: New BugsAssignee: WebKit Review Bot <webkit.review.bot>
Status: RESOLVED FIXED    
Severity: Normal CC: jchaffraix, roger_fong, tony
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
ROLLOUT of r143536 none

WebKit Review Bot
Reported 2013-02-21 15:44:44 PST
http://trac.webkit.org/changeset/143536 broke the build: Causing a bunch of tests to fail on Windows, requires rebaselining (Requested by rfong on #webkit). This is an automatic bug report generated by the sheriff-bot. If this bug report was created because of a flaky test, please file a bug for the flaky test (if we don't already have one on file) and dup this bug against that bug so that we can track how often these flaky tests case pain. "Only you can prevent forest fires." -- Smokey the Bear
Attachments
ROLLOUT of r143536 (8.11 KB, patch)
2013-02-21 15:45 PST, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2013-02-21 15:45:14 PST
Created attachment 189622 [details] ROLLOUT of r143536 Any committer can land this patch automatically by marking it commit-queue+. The commit-queue will build and test the patch before landing to ensure that the rollout will be successful. This process takes approximately 15 minutes. If you would like to land the rollout faster, you can use the following command: webkit-patch land-attachment ATTACHMENT_ID where ATTACHMENT_ID is the ID of this attachment.
WebKit Review Bot
Comment 2 2013-02-21 15:52:04 PST
Comment on attachment 189622 [details] ROLLOUT of r143536 Clearing flags on attachment: 189622 Committed r143658: <http://trac.webkit.org/changeset/143658>
WebKit Review Bot
Comment 3 2013-02-21 15:52:07 PST
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.