Bug 151364 - storage/indexeddb/modern/get-index-failures.html flakily times out on mac-wk1
Summary: storage/indexeddb/modern/get-index-failures.html flakily times out on mac-wk1
Status: RESOLVED DUPLICATE of bug 151507
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
Depends on:
Blocks: 149117
  Show dependency treegraph
Reported: 2015-11-17 15:12 PST by Ryan Haddad
Modified: 2015-11-20 12:24 PST (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Haddad 2015-11-17 15:12:47 PST
--- /Volumes/Data/slave/elcapitan-debug-tests-wk1/build/layout-test-results/storage/indexeddb/modern/get-index-failures-expected.txt
+++ /Volumes/Data/slave/elcapitan-debug-tests-wk1/build/layout-test-results/storage/indexeddb/modern/get-index-failures-actual.txt
@@ -1,12 +1,8 @@
+FAIL: Timed out waiting for notifyDone to be called
 This tests some obvious failures that can happen while calling IDBObjectStore.index().
 Initial upgrade needed: Old version - 0 New version - 1
 Initial upgrade versionchange transaction complete
 Got an index as expected: [object IDBIndex]
 Failed to get an index with a null name
 Failed to get an index that doesn't exist
-readonly transaction complete
-Second upgrade needed: Old version - 1 New version - 2
-Failed to get an index from a deleted object store
-Second versionchange transaction complete

Comment 1 Ryan Haddad 2015-11-17 15:16:08 PST
Marked as flaky in <https://trac.webkit.org/r192545>
Comment 2 Brady Eidson 2015-11-20 10:37:44 PST
This timeout is because an IDBTransaction callback was never received in javascript on the test web page.

This could be because the IDBTransaction's wrapper was garbage collected, so the callback could not be made.

I noticed this happening while working on https://bugs.webkit.org/show_bug.cgi?id=151456, and it will be fixed when that patch lands.

This might go away after that.
Comment 3 Brady Eidson 2015-11-20 12:24:29 PST

*** This bug has been marked as a duplicate of bug 151507 ***