161249 2016-08-26 09:14:10 -0700 REGRESSION (r204601): Many new flaky timeouts started on 8/18/16 2016-08-31 15:20:22 -0700 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=161208 https://bugs.webkit.org/show_bug.cgi?id=161210 https://bugs.webkit.org/show_bug.cgi?id=161157 https://bugs.webkit.org/show_bug.cgi?id=161164 https://bugs.webkit.org/show_bug.cgi?id=161279 https://bugs.webkit.org/show_bug.cgi?id=161144 https://bugs.webkit.org/show_bug.cgi?id=160652 https://bugs.webkit.org/show_bug.cgi?id=161141 https://bugs.webkit.org/show_bug.cgi?id=161205 P2 Normal --- 1 ryanhaddad webkit-unassigned ap eric.carlson oldest_to_newest 1223529 0 ryanhaddad 2016-08-26 09:14:10 -0700 There have been a large number of flaky tests that all started timing out around 8/18/16. 1224203 1 ap 2016-08-29 10:28:37 -0700 This is very likely caused by <http://trac.webkit.org/r204601>, even though there is no obvious relationship to the failing tests. The failures are rare, but cross-referencing multiple tests and multiple bots, I found that there are no timeouts on these before r204601, and then there are 2-3 failures for each revision. The timeout happens in the same worker that ran hls/hls-accessiblity-describes-video-menu.html, only 2-3 minutes later. 1224333 2 ap 2016-08-29 14:02:12 -0700 Ryan skipped hls/hls-accessiblity-describes-video-menu.html in r205124 to see if it helps. 1225099 3 ap 2016-08-31 14:52:50 -0700 Well, that did it. Still a mystery why this test causes timeouts later.