storage/indexeddb/modern/blob-cursor.html is flaky timing out and started around commit 252956 but it is flaky so I am unsure if this was the commit that caused the issue. I did not try to reproduce the timeout, this is happening on Catalina and Mojave with wk1 History: https://results.webkit.org/?suite=layout-tests&test=storage%2Findexeddb%2Fmodern%2Fblob-cursor.html Diff: --- /Volumes/Data/slave/catalina-debug-tests-wk1/build/layout-test-results/storage/indexeddb/modern/blob-cursor-expected.txt +++ /Volumes/Data/slave/catalina-debug-tests-wk1/build/layout-test-results/storage/indexeddb/modern/blob-cursor-actual.txt @@ -1,13 +1,2 @@ -Now let's retrieve the blobs using a cursor. -Got item from cursor -Got item from cursor -Finished cursor -blobResults.length is 2 - Result 0 is [object Blob] - Result 1 is [object Blob] -Image 0 loaded successfully -Image 1 loaded successfully -PASS successfullyParsed is true - -TEST COMPLETE - +FAIL: Timed out waiting for notifyDone to be called +Click to start test in new window
<rdar://problem/58838711>
I tried to reproduce this by running in iteration but was unsuccessful.
I'm not confident that this is a regression. Increasing the history limit, I see much older timeouts too. This test has unusually inconsistent run time. I see everything including 1 second, 10 seconds, 25 seconds, timeout... Not sure what about IndexedDB causes such inconsistency.
Created attachment 389016 [details] Update Test Expectations
Comment on attachment 389016 [details] Update Test Expectations Clearing flags on attachment: 389016 Committed r255247: <https://trac.webkit.org/changeset/255247>
This should be fixed after https://bugs.webkit.org/show_bug.cgi?id=206971.