Bug 69368

Summary: REGRESSION(r96630): Caused assertion failures in validateCell (Requested by mhahnenberg 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: darin, mhahnenberg
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 69311    
Attachments:
Description Flags
ROLLOUT of r96630 none

WebKit Review Bot
Reported 2011-10-04 13:32:49 PDT
http://trac.webkit.org/changeset/96630 broke the build: Caused assertion failures in validateCell (Requested by mhahnenberg 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 r96630 (10.43 KB, patch)
2011-10-04 13:33 PDT, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2011-10-04 13:33:15 PDT
Created attachment 109671 [details] ROLLOUT of r96630 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 2011-10-04 13:37:04 PDT
Comment on attachment 109671 [details] ROLLOUT of r96630 Clearing flags on attachment: 109671 Committed r96637: <http://trac.webkit.org/changeset/96637>
WebKit Review Bot
Comment 3 2011-10-04 13:37:08 PDT
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.