http://trac.webkit.org/changeset/79774 broke the build: WebKit/chromium change broke chromium port. I'll cq+ it in 15 minutes. Chime in if you have a fix. (Requested by pfeldman 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
Created attachment 83939 [details] ROLLOUT of r79774 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.
I'm not sure if this is a real failure. It's compiling on build.chromium.org so it could be that we just need a clobbering on webkit.org bots.
(In reply to comment #2) > I'm not sure if this is a real failure. It's compiling on build.chromium.org so it could be that we just need a clobbering on webkit.org bots. I think clobbering the WebKit Chromium bots should resolve this. See https://bugs.webkit.org/show_bug.cgi?id=44797#c20.
(In reply to comment #3) > (In reply to comment #2) > > I'm not sure if this is a real failure. It's compiling on build.chromium.org so it could be that we just need a clobbering on webkit.org bots. > > I think clobbering the WebKit Chromium bots should resolve this. See https://bugs.webkit.org/show_bug.cgi?id=44797#c20. The Chromium Win bot is passing now. This can be closed.