Bug 87633 - Application cache abort() tests are flaky
Summary: Application cache abort() tests are flaky
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
: 141368 (view as bug list)
Depends on:
Reported: 2012-05-28 01:23 PDT by Chris Dumez
Modified: 2018-03-20 17:37 PDT (History)
4 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Chris Dumez 2012-05-28 01:23:33 PDT
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.

It appears that the Application Cache download process could not be aborted in time and the download completed/succeeded.
Comment 1 Alexey Proskuryakov 2015-02-08 11:01:53 PST
*** Bug 141368 has been marked as a duplicate of this bug. ***
Comment 2 Alexey Proskuryakov 2015-02-08 11:05:07 PST
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.
Comment 3 Alexey Proskuryakov 2015-02-08 11:11:56 PST
Updated expectations in r179798.