Bug 90749

Summary: REGRESSION(r121968): Caused a link error on chromium Win dbg. (Requested by hayato 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: hayato, yurys
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 90615    
Attachments:
Description Flags
ROLLOUT of r121968 none

Description WebKit Review Bot 2012-07-08 21:50:42 PDT
http://trac.webkit.org/changeset/121968 broke the build:
Caused a link error on chromium Win dbg. (Requested by hayato 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
Comment 1 WebKit Review Bot 2012-07-08 21:51:17 PDT
Created attachment 151182 [details]
ROLLOUT of r121968

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.
Comment 2 Hayato Ito 2012-07-08 21:53:11 PDT
See also https://bugs.webkit.org/show_bug.cgi?id=90745.
Comment 3 WebKit Review Bot 2012-07-08 21:59:29 PDT
Comment on attachment 151182 [details]
ROLLOUT of r121968

Clearing flags on attachment: 151182

Committed r122087: <http://trac.webkit.org/changeset/122087>
Comment 4 WebKit Review Bot 2012-07-08 21:59:33 PDT
All reviewed patches have been landed.  Closing bug.
Comment 5 Hayato Ito 2012-07-08 23:10:40 PDT
*** Bug 90745 has been marked as a duplicate of this bug. ***