Tests that carefully checks opt/deopt status shouldn't --always-opt.

Tests that carefully checks opt/deopt status shouldn't --always-opt.

If we optimize a function before gathering feedback it may be
peppered with soft deoptimizations. So it can't help but deoptimize.
A judicious reading of the code isn't enough to determine what the
optimization state should be in the face of such chaotic gyrations.

BUG=
R=verwaest@chromium.org

Committed: https://crrev.com/af293729ad51cbf611584d898733964bf0bec5e4
Cr-Commit-Position: refs/heads/master@{#27671}

[mvstanton, 2015-04-08 15:29:12]

Hi Toon,
Here is the test fix per our chat,
--Michael

[Toon Verwaest, 2015-04-08 15:30:14]

lgtm

[mvstanton, 2015-04-08 15:31:04]

The CQ bit was checked by mvstanton@chromium.org

[commit-bot: I haz the power, 2015-04-08 15:31:21]

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

[commit-bot: I haz the power, 2015-04-08 15:56:04]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-04-08 15:56:16]

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