Re-enable ensemble tests on Windows Release builds.

Re-enable ensemble tests on Windows Release builds.

This is only taking a long time on Debug, because of the additional iterator
validators running on all the stl objects being used.

BUG=101614
Committed: https://crrev.com/6e7226194f0c3390dd07829098f9da132bca03c5
Cr-Commit-Position: refs/heads/master@{#299437}

[Will Harris, 2014-10-10 18:57:29]

wfh@chromium.org changed reviewers:
+ dgarrett@chromium.org

[Will Harris, 2014-10-10 18:57:29]

Evidence for this change:

Running in Debug, VersioningTest.All takes 3345ms:

[42/45] VersioningTest.All (3345 ms)

Running in Release, ensemble tests take around the same time:

[39/48] EnsembleTest.PE (3675 ms)
[40/48] EnsembleTest.PE64 (2429 ms)
[41/48] EnsembleTest.Elf32 (472 ms)

So, each ensemble test in Release (across equivalent code: both VersioningTest
and EnsembleTest exercise the same code) take around the same time as the
longest test in Debug, so I can't see any reason why we can't re-enable the
three EnsembleTests in Release.

[Will Harris, 2014-10-10 19:49:55]

results from the bots confirm that I think this should be okay:

win_chromium_rel speeds:

[39/48] EnsembleTest.PE (4618 ms)
[40/48] EnsembleTest.PE64 (5054 ms)
[41/48] EnsembleTest.Elf32 (577 ms)

win_chromium_x64_rel speeds:

[39/48] EnsembleTest.PE (4602 ms)
[40/48] EnsembleTest.PE64 (3776 ms)
[41/48] EnsembleTest.Elf32 (515 ms)

[dgarrett, 2014-10-14 01:50:16]

LGTM

[Will Harris, 2014-10-14 02:05:47]

The CQ bit was checked by wfh@chromium.org

[Will Harris, 2014-10-14 02:05:55]

The CQ bit was checked by wfh@chromium.org

[commit-bot: I haz the power, 2014-10-14 02:06:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/647093002/1

[commit-bot: I haz the power, 2014-10-14 02:09:22]

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

[commit-bot: I haz the power, 2014-10-14 02:09:23]

Try jobs failed on following builders:
  linux_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu_trigger...)
  mac_gpu_retina_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu_retina_tr...)
  mac_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu_triggered...)
  win_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu_triggered...)

[Will Harris, 2014-10-14 06:10:47]

The CQ bit was checked by wfh@chromium.org

[commit-bot: I haz the power, 2014-10-14 06:11:48]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/647093002/1

[commit-bot: I haz the power, 2014-10-14 06:12:15]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-10-14 06:17:39]

Patchset 1 (id:??) landed as
https://crrev.com/6e7226194f0c3390dd07829098f9da132bca03c5
Cr-Commit-Position: refs/heads/master@{#299437}