|Summary:||storage/indexeddb/modern/256-open-databases.html frequently times out on WK2|
|Product:||WebKit||Reporter:||Ryan Haddad <ryanhaddad>|
|Component:||WebCore Misc.||Assignee:||Nobody <webkit-unassigned>|
|Version:||WebKit Nightly Build|
|Bug Depends on:||155041|
Description Ryan Haddad 2016-03-04 11:28:40 PST
storage/indexeddb/modern/256-open-databases.html frequently times out on Mac <https://build.webkit.org/builders/Apple%20Yosemite%20Release%20WK2%20(Tests)/builds/12557> <http://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=storage%2Findexeddb%2Fmodern%2F256-open-databases.html> --- /Volumes/Data/slave/yosemite-release-tests-wk2/build/layout-test-results/storage/indexeddb/modern/256-open-databases-expected.txt +++ /Volumes/Data/slave/yosemite-release-tests-wk2/build/layout-test-results/storage/indexeddb/modern/256-open-databases-actual.txt @@ -1,12 +1,2 @@ -This test makes sure that if you open 128 unique databases, close your connections to them, and then open 128 other unique databases, that it works. +FAIL: Timed out waiting for notifyDone to be called -On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". - - -Opened the first 128 databases. Now closing them... -Now opening the second 128 databases -Successfully opened 256 databases (after closing the first 128) -PASS successfullyParsed is true - -TEST COMPLETE -
Comment 1 Ryan Haddad 2016-03-04 13:18:49 PST
Skipped test in <http://trac.webkit.org/projects/webkit/changeset/197583>
Comment 2 Alexey Proskuryakov 2016-03-05 14:55:22 PST
Looks like it may need to be skipped on WK1 too (and I bet all other platforms).
Comment 3 Brady Eidson 2016-03-07 14:39:42 PST
The reason for this timeout is well understood, and is an infrastructure issue. Should not block the umbrella bug.
Comment 4 Brady Eidson 2016-06-03 11:09:42 PDT
This was timing out in all bot configs for a large span of time, but then around 5/26-5/27 it stopped timing out. There's still *very* frequent text failures like the following: --- /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/storage/indexeddb/intversion-open-in-upgradeneeded-expected.txt +++ /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/storage/indexeddb/intversion-open-in-upgradeneeded-actual.txt @@ -34,8 +34,6 @@ onVersionChange(): db.close() -onBlocked(): - upgradeNeeded2(): db = event.target.result PASS event.newVersion is 3 That might be a test bug. I'll look in to that.
Comment 5 Brady Eidson 2016-06-03 11:11:24 PDT
(In reply to comment #4) > This was timing out in all bot configs for a large span of time, but then > around 5/26-5/27 it stopped timing out. > > There's still *very* frequent text failures like the following: > > --- > /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/ > storage/indexeddb/intversion-open-in-upgradeneeded-expected.txt > +++ > /Volumes/Data/slave/elcapitan-debug-tests-wk2/build/layout-test-results/ > storage/indexeddb/intversion-open-in-upgradeneeded-actual.txt > @@ -34,8 +34,6 @@ > onVersionChange(): > db.close() > > -onBlocked(): > - > upgradeNeeded2(): > db = event.target.result > PASS event.newVersion is 3 > > That might be a test bug. I'll look in to that. This comment belongs in a different bug.
Comment 6 Brady Eidson 2016-07-04 22:24:15 PDT
According to the test history, I think this hasn't timed out (at least since the master was last rebooted) Ryan, am I right about that? Can we close this one?
Comment 7 Brady Eidson 2016-07-13 16:51:01 PDT
*sigh* never mind, it's skipped. that's why.