WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
Bug 68146
REGRESSION(
r95174
): Broke Chromium builds in a way that wasn't obviously fixable. (Requested by dave_levin on #webkit).
https://bugs.webkit.org/show_bug.cgi?id=68146
Summary
REGRESSION(r95174): Broke Chromium builds in a way that wasn't obviously fixa...
WebKit Review Bot
Reported
2011-09-15 00:41:10 PDT
http://trac.webkit.org/changeset/95174
broke the build: Broke Chromium builds in a way that wasn't obviously fixable. (Requested by dave_levin 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 r95174
(10.74 KB, patch)
2011-09-15 00:41 PDT
,
WebKit Review Bot
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
WebKit Review Bot
Comment 1
2011-09-15 00:41:36 PDT
Created
attachment 107473
[details]
ROLLOUT of
r95174
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.
David Levin
Comment 2
2011-09-15 00:48:31 PDT
Comment on
attachment 107473
[details]
ROLLOUT of
r95174
The fix was pretty simple after all. I should obviously go to sleep.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug