RESOLVED INVALID56769
REGRESSION(r81601): Breaks GTK tests. (Requested by vsevik on #webkit). 
https://bugs.webkit.org/show_bug.cgi?id=56769
Summary REGRESSION(r81601): Breaks GTK tests. (Requested by vsevik on #webkit).
WebKit Review Bot
Reported 2011-03-21 14:14:55 PDT
http://trac.webkit.org/changeset/81601 broke the build: Breaks GTK tests. (Requested by vsevik 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 r81601 (900 bytes, patch)
2011-03-21 14:15 PDT, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2011-03-21 14:15:22 PDT
Created attachment 86364 [details] ROLLOUT of r81601 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.
Pavel Feldman
Comment 2 2011-03-21 14:21:15 PDT
Eric, sheriff bot failed to do the revert.
Pavel Feldman
Comment 3 2011-03-21 14:22:41 PDT
Ok, this is not cq, this is bot. Adding Adam. I should add both of you at all times not to make mistakes.
Adam Barth
Comment 4 2011-03-21 15:06:20 PDT
Interesting. Thanks. Maybe the sheriffbot doesn't understand how to deal with rename-only patches correctly?
Eric Seidel (no email)
Comment 5 2011-03-21 17:05:08 PDT
I think Adam and I need to spend another week or two fixing all these recent annoyances with the scripts. I'm not sure what the deal with this patch failure is.
Note You need to log in before you can comment on or make changes to this bug.