Bug 110242

Summary: REGRESSION(r143348): "Caused a deleted value sentinel crash on the layout tests" (Requested by ggaren 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: ggaren, oliver
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 110179    
Attachments:
Description Flags
ROLLOUT of r143348 none

WebKit Review Bot
Reported 2013-02-19 11:32:48 PST
http://trac.webkit.org/changeset/143348 broke the build: "Caused a deleted value sentinel crash on the layout tests" (Requested by ggaren 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 r143348 (4.39 KB, patch)
2013-02-19 11:33 PST, WebKit Review Bot
no flags
WebKit Review Bot
Comment 1 2013-02-19 11:33:18 PST
Created attachment 189122 [details] ROLLOUT of r143348 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-02-19 11:41:35 PST
Comment on attachment 189122 [details] ROLLOUT of r143348 Clearing flags on attachment: 189122 Committed r143366: <http://trac.webkit.org/changeset/143366>
WebKit Review Bot
Comment 3 2013-02-19 11:41:38 PST
All reviewed patches have been landed. Closing bug.
Geoffrey Garen
Comment 4 2013-02-19 14:30:36 PST
Note You need to log in before you can comment on or make changes to this bug.