Bug 56567 – Flaky Test: http/tests/cache/history-only-cached-subresource-loads.html

• Status: NEW
• Component: Tools / Tests

[WebKit Commit Bot]

This is an automatically generated bug from the commit-queue.
http/tests/cache/history-only-cached-subresource-loads.html has been flaky on the commit-queue.

http/tests/cache/history-only-cached-subresource-loads.html was authored by [e-mail].
http://trac.webkit.org/browser/trunk/LayoutTests/http/tests/cache/history-only-cached-subresource-loads.html

The commit-queue just saw http/tests/cache/history-only-cached-subresource-loads.html flake (Test timed out) while processing attachment 86027 [details] on bug 55658.
Bot: cr-jail-7  Port: Mac  Platform: Mac OS X 10.6.6

The bots will update this with information from each new failure.

If you believe this bug to be fixed or invalid, feel free to close.  The bots will re-open if the flake re-occurs.

If you would like to track this test fix with another bug, please close this bug as a duplicate.  The bots will follow the duplicate chain when making future comments.

[WebKit Commit Bot]

Created attachment 86065 [details]
Archive of layout-test-results from cr-jail-7

[Raphael Kubo da Costa (:rakuco)]

Seems to have started happening on EFL as well. From <http://build.webkit.org/results/EFL%20Linux%2064-bit%20Debug/r130761%20%286932%29/http/tests/cache/history-only-cached-subresource-loads-diff.txt>:

--- /home/buildslave-1/webkit-buildslave/efl-linux-64-debug/build/layout-test-results/http/tests/cache/history-only-cached-subresource-loads-expected.txt
+++ /home/buildslave-1/webkit-buildslave/efl-linux-64-debug/build/layout-test-results/http/tests/cache/history-only-cached-subresource-loads-actual.txt
@@ -1,8 +1,6 @@
+FAIL: Timed out waiting for notifyDone to be called
 This test checks that loading a subresource with "Cache-Control: no-store" is cached and reused in back navigation when the page is not in the page cache.
 
 We then test that loading the same subresource is refetched when used in non-stale loads such as refreshes or normal navigation.
 
-PASS - no-store subresource was cached and used for a back navigation
-PASS - no-store subresource was refetched with a reload
-PASS - no-store subresource was refetched with a normal navigation