86014 2012-05-09 13:56:55 -0700 Chromium perf bots fail to download the binary ~50% of the time 2012-09-20 20:08:42 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED LATER P2 Normal --- 77037 1 ojan webkit-unassigned abarth morrita rniwa tony oldest_to_newest 619808 0 ojan 2012-05-09 13:56:55 -0700 This means we're losing a lot of coverage. Not sure who manages these bots... http://build.webkit.org/waterfall?show=Chromium%20Win%20Release%20(Perf)&show=Chromium%20Mac%20Release%20(Perf)&show=Chromium%20Linux%20Release%20(Perf) 619859 1 rniwa 2012-05-09 14:45:57 -0700 This is because perf bots' cycle time is significantly longer than that of builders especially when changes are trivial. perf. bots get behind, and hits master's threshold to delete uploaded binaries. I've asked wms to increase the threadshold but it didn't help. The only thing it did was increasing the delay and backlogs. The only solution to this problem is reducing cycle time of perf bots. Otherwise, the backlog will grow indefinitely. 619865 2 tony 2012-05-09 14:47:10 -0700 Do we know which tests are the slowest? Maybe we can get a better cycle time just by fixing a dozen or so tests. 619871 3 rniwa 2012-05-09 14:52:18 -0700 Yeah, most of them are Dromaeo tests. We spend roughly 30% of time running the slowest 5 tests. You can process the stdout on bots to find the ranking although I've posted somewhere on Bugzilla as well. 673997 4 rniwa 2012-07-19 15:43:24 -0700 We don't have any workable solution for this at the moment.