http://trac.webkit.org/changeset/59483 broke the build: "page_cycler_intl1 regression on Linux" (Requested by yurys 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 56238 [details] ROLLOUT of r59483 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 see a big spike after WebKit roll 59478:59601 in Chromium: http://build.chromium.org/buildbot/perf/linux-release-hardy/intl1/report.html?history=150&rev=-1&graph=write_op_b I ran Chromium with different WebKit versions and got w_op_b = 23423 with 59482, and w_op_b=25541 with r59483 so I'm pretty sure it's this patch to blame.
Comment on attachment 56238 [details] ROLLOUT of r59483 Committing to http://svn.webkit.org/repository/webkit/trunk ... M WebCore/ChangeLog M WebCore/platform/chromium/ChromiumBridge.h M WebCore/platform/graphics/chromium/FontCacheLinux.cpp Committed r59607