IndexedDB: Test updates for store/index deletion race

IndexedDB: Test updates for store/index deletion race

Follow-up to https://codereview.chromium.org/277583002 to rework test
and add new one. createIndex-after-failure.html now matches FF behavior.

BUG=370056, 368271
TBR=ericu@chromium.org

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=174727

[jsbell, 2014-05-23 19:18:49]

cmumford@ - please take a look?

[cmumford, 2014-05-23 19:57:20]

lgtm

https://codereview.chromium.org/291243003/diff/20001/LayoutTests/storage/inde...
File LayoutTests/storage/indexeddb/resources/createIndex-after-failure.js
(right):

https://codereview.chromium.org/291243003/diff/20001/LayoutTests/storage/inde...
LayoutTests/storage/indexeddb/resources/createIndex-after-failure.js:41:
evalAndExpectException("objectStore.deleteIndex('index')", "0",
"'TransactionInactiveError'");
Just curious: why two calls to deleteIndex?

[jsbell, 2014-05-23 20:09:10]

https://codereview.chromium.org/291243003/diff/20001/LayoutTests/storage/inde...
File LayoutTests/storage/indexeddb/resources/createIndex-after-failure.js
(right):

https://codereview.chromium.org/291243003/diff/20001/LayoutTests/storage/inde...
LayoutTests/storage/indexeddb/resources/createIndex-after-failure.js:41:
evalAndExpectException("objectStore.deleteIndex('index')", "0",
"'TransactionInactiveError'");
On 2014/05/23 19:57:20, cmumford wrote:
> Just curious: why two calls to deleteIndex?

I believe this test started life as a regression test for a crash triggered by a
second deleteIndex(). It's in the initial commit of the test and no comment, so
it's hard to tell.

[jsbell, 2014-05-23 20:09:15]

The CQ bit was checked by jsbell@chromium.org

[commit-bot: I haz the power, 2014-05-23 20:09:29]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jsbell@chromium.org/291243003/20001

[commit-bot: I haz the power, 2014-05-23 20:09:30]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-05-23 20:09:31]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[jsbell, 2014-05-23 20:54:45]

The CQ bit was checked by jsbell@chromium.org

[commit-bot: I haz the power, 2014-05-23 20:55:27]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jsbell@chromium.org/291243003/20001

[commit-bot: I haz the power, 2014-05-23 22:13:32]

FYI, CQ is re-trying this CL (attempt #1).
Please consider checking whether the failures are real,
and report flakes to chrome-troopers@google.com.
The failing builders are:
  win_blink_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/win_blink_rel/builds/8997)

[commit-bot: I haz the power, 2014-05-23 23:01:30]

Change committed as 174727

[ericu, 2014-05-27 21:21:44]

LGTM2