Bug 105917

Summary: REGRESSION(r138601): Also not an optimal solution, needs more discussion. (Requested by mkwst_ 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: eric, mkwst
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 103539    
Attachments:
Description Flags
ROLLOUT of r138601 none

WebKit Review Bot
Reported 2013-01-02 04:05:29 PST
http://trac.webkit.org/changeset/138601 broke the build: Also not an optimal solution, needs more discussion. (Requested by mkwst_ 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 r138601 (6.47 KB, patch)
2013-01-02 04:06 PST, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2013-01-02 04:06:18 PST
Created attachment 181024 [details] ROLLOUT of r138601 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-01-02 04:21:06 PST
Comment on attachment 181024 [details] ROLLOUT of r138601 Clearing flags on attachment: 181024 Committed r138616: <http://trac.webkit.org/changeset/138616>
WebKit Review Bot
Comment 3 2013-01-02 04:21:09 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.