Bug 164870

Summary: [mac-wk2 debug] LayoutTest imported/w3c/web-platform-tests/IndexedDB/idbcursor_iterating.htm is a flaky failure
Product: WebKit Reporter: Ryan Haddad <ryanhaddad>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: beidson, joepeck, sihui_liu, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Other   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 154968    

Ryan Haddad
Reported 2016-11-17 09:30:01 PST
LayoutTest imported/w3c/web-platform-tests/IndexedDB/idbcursor_iterating.htm is a flaky failure https://build.webkit.org/results/Apple%20El%20Capitan%20Debug%20WK2%20(Tests)/r208845%20(9491)/results.html --- /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/IndexedDB/idbcursor_iterating-expected.txt +++ /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/IndexedDB/idbcursor_iterating-actual.txt @@ -1,3 +1,3 @@ -PASS IDBCursor.continue() - objectstore - delete next element, and iterate to it +TIMEOUT IDBCursor.continue() - objectstore - delete next element, and iterate to it Test timed out
Attachments
Ryan Haddad
Comment 1 2016-11-17 10:20:27 PST
Brady Eidson
Comment 2 2016-11-17 13:45:15 PST
It is only on the verge of timing out in debug builds - Plenty fast in release builds.
Brady Eidson
Comment 3 2016-11-17 13:45:41 PST
(And I see you only marked it flaky for Debug! Great!)
Brady Eidson
Comment 4 2016-12-02 09:35:25 PST
This timing out is not a real correctness bug, but rather a real performance bug. We need to speed up cursors in general, specifically for debug builds of course. We'll need to have cursors prefetch the next record or two.
Joseph Pecoraro
Comment 5 2018-08-09 17:07:35 PDT
Closing. El Capitan expectations have been removed.
Radar WebKit Bug Importer
Comment 6 2018-08-09 17:08:27 PDT
Sihui Liu
Comment 7 2021-07-30 10:26:08 PDT
Expectations updated at https://bugs.webkit.org/show_bug.cgi?id=228241 as the test is no longer flaky.
Note You need to log in before you can comment on or make changes to this bug.