Bug 151364
| Summary: | storage/indexeddb/modern/get-index-failures.html flakily times out on mac-wk1 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ryan Haddad <ryanhaddad> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | beidson |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 149117 | ||
Ryan Haddad
--- /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
-Done
Run:
<https://build.webkit.org/builders/Apple%20El%20Capitan%20Debug%20WK1%20(Tests)/builds/1182>
Results:
<https://build.webkit.org/results/Apple%20El%20Capitan%20Debug%20WK1%20(Tests)/r192529%20(1182)/results.html>
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ryan Haddad
Marked as flaky in <https://trac.webkit.org/r192545>
Brady Eidson
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.
Brady Eidson
*** This bug has been marked as a duplicate of bug 151507 ***