36931 2010-03-31 23:20:04 -0700 http/tests/appcache/cyrillic-uri.html timed out on Snow Leopard Release Bot 2010-04-06 04:52:52 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) PC OS X 10.5 NEW P2 Normal --- 33292 1 eric webkit-unassigned ap darin ossy oldest_to_newest 206975 0 eric 2010-03-31 23:20:04 -0700 http/tests/appcache/cyrillic-uri.html timed out on Snow Leopard Release Bot http://build.webkit.org/results/SnowLeopard%20Intel%20Release%20(Tests)/r56895%20(7511)/http/tests/appcache/cyrillic-uri-diffs.txt --- /Volumes/Data/WebKit-BuildSlave/snowleopard-intel-release-tests/build/layout-test-results/http/tests/appcache/cyrillic-uri-expected.txt 2010-03-31 22:17:55.000000000 -0700 +++ /Volumes/Data/WebKit-BuildSlave/snowleopard-intel-release-tests/build/layout-test-results/http/tests/appcache/cyrillic-uri-actual.txt 2010-03-31 22:17:55.000000000 -0700 @@ -1,3 +1,4 @@ +FAIL: Timed out waiting for notifyDone to be called Test that non-ASCII URIs work correctly in cache manifests. Should be a series of PASS messages, followed with DONE. @@ -9,5 +10,4 @@ PASS: resources/intercept/network-Проверка-PASS PASS: resources/intercept/network-%D0%9F%D1%80%D0%BE%D0%B2%D0%B5%D1%80%D0%BA%D0%B0-PASS PASS: resources/does-not-exist-Проверка -DONE http://trac.webkit.org/browser/trunk/LayoutTests/http/tests/appcache/cyrillic-uri.html 207012 1 ap 2010-04-01 00:21:20 -0700 I'm not sure why we need bugs for each test timeout. There is nothing possibly flaky in most of these tests - it seems to be some general issue, so we could as well end up with a bug for every test. 207014 2 eric 2010-04-01 00:22:34 -0700 Bugs give us a permanent record. We can always dup them to some root cause once we have some clue what that cause is. 207017 3 ap 2010-04-01 00:28:54 -0700 How would a person fixing a flaky bit of code know which of the unreproducible bugs were caused by it? Or how would we know it if it's fixed by a CFNetwork or even lower level change? Perhaps you could consider using wiki for keeping track of infrequent failures such as this. 207026 4 eric 2010-04-01 00:40:03 -0700 Chromium has a flakiness dashboard which is automatically kept up to date based on real data from the bots. That would be a better solution than our current ad-hoc bug solution. However this ad-hoc bug solution is better than ignoring the bots. Note that the bots have become way greener since we've started filing failures about them in bugs.webkit.org. :) 208988 5 ossy 2010-04-06 04:52:52 -0700 timed out: http://build.webkit.org/results/SnowLeopard%20Intel%20Release%20%28Tests%29/r57141%20%287751%29/results.html failed: http://build.webkit.org/results/SnowLeopard%20Intel%20Release%20%28Tests%29/r57141%20%287750%29/results.html