Re-enable all (but four) IndexedDB content browser tests on Android.

Re-enable all (but four) IndexedDB content browser tests on Android.

Tested by running all IndexedDB tests (40 times) on the following devices:

1. Nexus 7: 4.4.3
2. Nexus 4: 4.2.2
3. Galaxy Nexus: 4.0.4

IndexedDBBrowserTestSingleProcess.RenderThreadShutdownTest is still
disabled - just in the standard way for Android.

BUG=256184, 233118
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=287030

[klundberg, 2014-06-20 21:56:08]

+Victor as he is working on content_browsertests

[jsbell, 2014-06-20 21:58:42]

lgtm

[dgrogan, 2014-06-20 22:45:25]

What ended up being the culprit?

[cmumford, 2014-06-23 16:03:57]

On 2014/06/20 22:45:25, dgrogan wrote:
> What ended up being the culprit?

Don't know yet. Instead of disabling all IndexedDB tests I just went and
explicitly disabled the failing tests, and then did my best to ensure that the
others passed consistently. There are currently four tests (bug numbers are in
the content_browsertests_disabled file). Two of those I have fixes for, and will
be pushing the CL's up for shortly. I think that so much has changed since these
tests were disabled that the actual cause of flakyness was fixed previously and
we just never got around to testing/reenabling these tests.

[cmumford, 2014-06-23 16:04:15]

The CQ bit was checked by cmumford@chromium.org

[commit-bot: I haz the power, 2014-06-23 16:04:59]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/cmumford@chromium.org/342413004/1

[cmumford, 2014-06-23 17:41:42]

The CQ bit was unchecked by cmumford@chromium.org

[cmumford, 2014-06-23 17:43:25]

On 2014/06/23 17:41:42, cmumford wrote:
> The CQ bit was unchecked by mailto:cmumford@chromium.org

I didn't see that other reviewers were added so I unchecked the CQ bit so that
others could review/comment.

[jsbell, 2014-07-10 19:47:47]

What's the plan here? Still waiting for reviews?

[cmumford, 2014-07-14 17:12:56]

On 2014/07/10 19:47:47, jsbell wrote:
> What's the plan here? Still waiting for reviews?

Yes - forgot to ping reviewers - <hint> <hint>

[Victor Starodub, 2014-07-14 18:33:20]

lgtm

But we had quite a few race conditions w/content_browsertests, so these might
turn out to be flaky on bots.

[cmumford, 2014-07-14 18:40:13]

On 2014/07/14 18:33:20, Victor Starodub wrote:
> lgtm
> 
> But we had quite a few race conditions w/content_browsertests, so these might
> turn out to be flaky on bots.

Thx Victor. If you can think of a way that I can test these prior to landing I'm
happy to run those tests. I don't want to make the bots any worse than they are.

[Victor Starodub, 2014-07-14 18:55:46]

I don't think there's much we can test separately here apart from running on
trybots.

Let's keep an eye on them and be ready to roll back. I can look into these if
they turn out to be flaky.

[cmumford, 2014-07-17 18:20:38]

Ping for other reviewers.

[cmumford, 2014-07-31 20:59:42]

The CQ bit was checked by cmumford@chromium.org

[commit-bot: I haz the power, 2014-07-31 21:02:45]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/cmumford@chromium.org/342413004/1

[commit-bot: I haz the power, 2014-08-01 17:18:30]

Change committed as 287030