87633 2012-05-28 01:23:33 -0700 Application cache abort() tests are flaky 2018-03-20 17:37:03 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=76270 https://bugs.webkit.org/show_bug.cgi?id=183684 P2 Normal --- 1 cdumez webkit-unassigned ap gyuyoung.kim lucas.de.marchi sw0524.lee oldest_to_newest 634983 0 cdumez 2012-05-28 01:23:33 -0700 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. 1067677 1 ap 2015-02-08 11:01:53 -0800 *** Bug 141368 has been marked as a duplicate of this bug. *** 1067679 2 ap 2015-02-08 11:05:07 -0800 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. 1067681 3 ap 2015-02-08 11:11:56 -0800 Updated expectations in r179798.