RESOLVED FIXED 111478
REGRESSION(r144798): "broke chromium windows build" (Requested by dpranke on #webkit). 
https://bugs.webkit.org/show_bug.cgi?id=111478
Summary REGRESSION(r144798): "broke chromium windows build" (Requested by dpranke on ...
WebKit Review Bot
Reported 2013-03-05 13:38:21 PST
http://trac.webkit.org/changeset/144798 broke the build: "broke chromium windows build" (Requested by dpranke 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 r144798 (93.52 KB, patch)
2013-03-05 13:38 PST, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2013-03-05 13:38:51 PST
Created attachment 191554 [details] ROLLOUT of r144798 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.
Dirk Pranke
Comment 2 2013-03-05 13:40:25 PST
Comment on attachment 191554 [details] ROLLOUT of r144798 Clearing flags on attachment: 191554 Committed r144810: <http://trac.webkit.org/changeset/144810>
Dirk Pranke
Comment 3 2013-03-05 13:40:27 PST
All reviewed patches have been landed. Closing bug.
Dirk Pranke
Comment 4 2013-03-05 13:41:26 PST
Looks like this breaks the windows build, so I'm rolling it out per dglazkov (since alec didn't appear to be around on #irc). Sorry! http://build.chromium.org/p/chromium.webkit/builders/WebKit%20Win%20Builder/builds/36731/steps/compile/logs/stdio
Note You need to log in before you can comment on or make changes to this bug.