The following test cases are consistently flaky on the bot: http/tests/appcache/abort-cache-onchecking-manifest-404.html = TEXT PASS http/tests/appcache/abort-cache-ondownloading-resource-404.html = TEXT PASS The diff looks like: --- /home/buildslave-1/webkit-buildslave/efl-linux-64-debug/build/layout-test-results/http/tests/appcache/abort-cache-onchecking-manifest-404-expected.txt +++ /home/buildslave-1/webkit-buildslave/efl-linux-64-debug/build/layout-test-results/http/tests/appcache/abort-cache-onchecking-manifest-404-actual.txt @@ -1,3 +1,2 @@ -CONSOLE MESSAGE: Application Cache download process was aborted. This tests that download process was aborted after checking event and before update failed. SUCCESS It appears that the Application Cache download process could not be aborted in time and the download completed/succeeded.
*** Bug 141368 has been marked as a duplicate of this bug. ***
These tests are intrinsically flaky - appcache progress events are for notification purposes only, so update progress can be at an entirely different stage when the event is dispatched. Notably, the tests with 404 responses can have the update already failed by the time "checking" event handled is called.
Updated expectations in r179798.