Bug 36931
| Summary: | http/tests/appcache/cyrillic-uri.html timed out on Snow Leopard Release Bot | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap, darin, ossy |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | OS X 10.5 | ||
| Bug Depends on: | |||
| Bug Blocks: | 33292 | ||
Eric Seidel (no email)
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
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
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.
Eric Seidel (no email)
Bugs give us a permanent record. We can always dup them to some root cause once we have some clue what that cause is.
Alexey Proskuryakov
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.
Eric Seidel (no email)
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. :)
Csaba Osztrogonác
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