Bug 44924

Summary: REGRESSION(r66418): Broke moving-shadow-on-container on multiple bots (Requested by abarth on #webkit).
Product: WebKit Reporter: WebKit Review Bot <webkit.review.bot>
Component: New BugsAssignee: WebKit Review Bot <webkit.review.bot>
Status: RESOLVED INVALID    
Severity: Normal CC: abarth, commit-queue, eric, krit, zimmermann
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Bug Depends on: 44928    
Bug Blocks: 44896    
Attachments:
Description Flags
ROLLOUT of r66418 none

WebKit Review Bot
Reported 2010-08-30 19:30:28 PDT
http://trac.webkit.org/changeset/66418 broke the build: Broke moving-shadow-on-container on multiple bots (Requested by abarth 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 r66418 (68.92 KB, patch)
2010-08-30 19:30 PDT, WebKit Review Bot
no flags
WebKit Review Bot
Comment 1 2010-08-30 19:30:49 PDT
Created attachment 66003 [details] ROLLOUT of r66418 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 --ignore-builders where ATTACHMENT_ID is the ID of this attachment.
Adam Barth
Comment 2 2010-08-30 20:35:56 PDT
Comment on attachment 66003 [details] ROLLOUT of r66418 The CQ doesn't want to land this patch. I bet it doesn't build anymore.
Eric Seidel (no email)
Comment 3 2010-08-30 20:50:26 PDT
Turns out it wasn't applying anymore. I landed it manually and filed bug 44928 about the cq problem.
Note You need to log in before you can comment on or make changes to this bug.