Bug 153849 - Layout Test imported/w3c/indexeddb/idbcursor-direction-index-keyrange.htm is flaky on Yosemite Release WK2
Summary: Layout Test imported/w3c/indexeddb/idbcursor-direction-index-keyrange.htm is ...
Status: RESOLVED DUPLICATE of bug 150854
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-03 17:20 PST by Ryan Haddad
Modified: 2016-02-04 11:36 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Haddad 2016-02-03 17:20:45 PST
Layout Test imported/w3c/indexeddb/idbcursor-direction-index-keyrange.htm is flaky on Yosemite Release WK2

Another flaky timeout on Yosemite Release WK2. It has been flaky for a while, but only seems to time out once every few days.
<https://build.webkit.org/builders/Apple%20Yosemite%20Release%20WK2%20(Tests)/builds/11711>
<https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fw3c%2Findexeddb%2Fidbcursor-direction-index-keyrange.htm>
Comment 1 Brady Eidson 2016-02-03 21:10:22 PST
As mentioned in b/153848:
Being flaky in WK2 is extremely unlikely to be a new issue, as nothing has changed for the WK2 implementation.
Comment 2 Brady Eidson 2016-02-03 21:11:29 PST
Things will change completely once https://bugs.webkit.org/show_bug.cgi?id=150854 is resolved.

I won't be looking into this bug independent of that.

We should skip if it's making the bots red.
Comment 3 Ryan Haddad 2016-02-04 11:13:21 PST
Skipped in <https://trac.webkit.org/r196133>
Comment 4 Brady Eidson 2016-02-04 11:36:23 PST
Now that it's skipped, and since the WK2-specific TestExpectations for IndexedDB will be removed along with https://bugs.webkit.org/show_bug.cgi?id=150854, this can be closed as a dupe.
Comment 5 Brady Eidson 2016-02-04 11:36:38 PST

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