Bug 161283 - Web Inspector: inspector/indexeddb/deleteDatabaseNamesWithSpace.html is flakey
Summary: Web Inspector: inspector/indexeddb/deleteDatabaseNamesWithSpace.html is flakey
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Joseph Pecoraro
URL:
Keywords: DoNotImportToRadar
Depends on:
Blocks:
 
Reported: 2016-08-26 19:15 PDT by Joseph Pecoraro
Modified: 2016-08-26 20:06 PDT (History)
9 users (show)

See Also:

Attachments
[PATCH] Proposed Fix (3.18 KB, patch)
2016-08-26 19:24 PDT, Joseph Pecoraro 		achristensen: review+
achristensen: commit-queue-
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Pecoraro 2016-08-26 19:15:40 PDT 
Summary:
inspector/indexeddb/deleteDatabaseNamesWithSpace.html is flakey

Steps to reproduce:
1. shell> run-webkit-tests inspector/indexeddb/deleteDatabaseNamesWithSpace.html --iterations=1000 --v
  => ~2 out of 1000 runs are failures on my system, more frequent on the bots

Notes:
- The tests deletes a database and then immediately checks what databases are available. Seems to be a race condition.
- Adding a short timeout between deleting and checking database names caused 0 in 10000 failures for me.
Comment 1 Joseph Pecoraro 2016-08-26 19:24:05 PDT 
Created attachment 287190 [details]
[PATCH] Proposed Fix
Comment 2 Alex Christensen 2016-08-26 19:38:04 PDT 
Comment on attachment 287190 [details]
[PATCH] Proposed Fix

View in context: https://bugs.webkit.org/attachment.cgi?id=287190&action=review

> LayoutTests/inspector/indexeddb/deleteDatabaseNamesWithSpace.html:27
> +            setTimeout(() => {

This should have a FIXME: This shouldn't be necessary.  Link to bugzilla assigned to Brady.
Comment 3 Joseph Pecoraro 2016-08-26 20:06:41 PDT 
<https://trac.webkit.org/changeset/205067>

Investigating real fix in bug 161285