RESOLVED FIXED 101155
REGRESSION(r133397): "Broke Qt. No way to force the damn bots to do a clean build. I'm giving up." (Requested by kbalazs on #webkit).
https://bugs.webkit.org/show_bug.cgi?id=101155
Summary REGRESSION(r133397): "Broke Qt. No way to force the damn bots to do a clean b...
WebKit Review Bot
Reported 2012-11-03 14:40:23 PDT
http://trac.webkit.org/changeset/133397 broke the build: "Broke Qt. No way to force the damn bots to do a clean build. I'm giving up." (Requested by kbalazs 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 r133397 (27.77 KB, patch)
2012-11-03 14:41 PDT, WebKit Review Bot
no flags
WebKit Review Bot
Comment 1 2012-11-03 14:41:00 PDT
Created attachment 172231 [details] ROLLOUT of r133397 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.
Balazs Kelemen
Comment 2 2012-11-03 14:43:10 PDT
Comment on attachment 172231 [details] ROLLOUT of r133397 Clearing flags on attachment: 172231 Committed r133400: <http://trac.webkit.org/changeset/133400>
Balazs Kelemen
Comment 3 2012-11-03 14:43:15 PDT
All reviewed patches have been landed. Closing bug.
Csaba Osztrogonác
Comment 4 2012-11-04 01:01:16 PST
Please don't blame the bots ... They are innocent.
Balazs Kelemen
Comment 5 2012-11-04 04:14:54 PST
Yes, finally I realized it was my fault. The weird thing however is that for me locally the build was always successful, and I believe that's because the old object files was still living my build and non-updated call sites used those. Sigh...
Note You need to log in before you can comment on or make changes to this bug.