This is an automatically generated bug from the commit-queue. storage/indexeddb/index-basics.html has been flaky on the commit-queue. storage/indexeddb/index-basics.html was authored by dgrogan@chromium.org and jsbell@chromium.org. http://trac.webkit.org/browser/trunk/LayoutTests/storage/indexeddb/index-basics.html The commit-queue just saw storage/indexeddb/index-basics.html flake (DumpRenderTree crashed) while processing attachment 127299 [details] on bug 78773. Bot: ec2-cq-01 Port: <class 'webkitpy.common.config.ports.ChromiumXVFBPort'> Platform: Linux-2.6.35-28-virtual-x86_64-with-Ubuntu-10.10-maverick The bots will update this with information from each new failure. If you believe this bug to be fixed or invalid, feel free to close. The bots will re-open if the flake re-occurs. If you would like to track this test fix with another bug, please close this bug as a duplicate. The bots will follow the duplicate chain when making future comments.
Why doesn't index-basics show up in http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20webkit.org&tests=indexeddb ?
The commit-queue just saw storage/indexeddb/index-basics.html flake (DumpRenderTree crashed) while processing attachment 128711 [details] on bug 79476. Bot: ec2-cq-01 Port: <class 'webkitpy.common.config.ports.ChromiumXVFBPort'> Platform: Linux-2.6.35-28-virtual-x86_64-with-Ubuntu-10.10-maverick
(In reply to comment #1) > Why doesn't index-basics show up in http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20webkit.org&tests=indexeddb ? Oh, because it flaked on the commit queue, not on a waterfall bot.
The commit-queue just saw storage/indexeddb/index-basics.html flake (DumpRenderTree crashed) while processing attachment 128535 [details] on bug 79388. Bot: ec2-cq-02 Port: <class 'webkitpy.common.config.ports.ChromiumXVFBPort'> Platform: Linux-2.6.35-28-virtual-x86_64-with-Ubuntu-10.10-maverick
Given that this crashed a grand total of 3 times total, only in a 3 day period 5 months ago, I think it's probably safe to resolve this.