Bug 52792

Summary: REGRESSION(r76172): This test still fails on the 32-bit GTK+ debug bot. (Requested by mrobinson 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: commit-queue, mrobinson
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Attachments:
Description Flags
ROLLOUT of r76172 none

WebKit Review Bot
Reported 2011-01-20 01:40:46 PST
http://trac.webkit.org/changeset/76172 broke the build: This test still fails on the 32-bit GTK+ debug bot. (Requested by mrobinson 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 r76172 (1.33 KB, patch)
2011-01-20 01:41 PST, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2011-01-20 01:41:06 PST
Created attachment 79563 [details] ROLLOUT of r76172 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.
WebKit Commit Bot
Comment 2 2011-01-20 02:42:35 PST
Comment on attachment 79563 [details] ROLLOUT of r76172 Clearing flags on attachment: 79563 Committed r76219: <http://trac.webkit.org/changeset/76219>
WebKit Commit Bot
Comment 3 2011-01-20 02:42:39 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.