Disable ParserSync test for now, it takes waaaaay too long.

Disable ParserSync test for now, it takes waaaaay too long.

Running this in x64.release mode on a powerful HP620 takes 4 seconds,
this is at least 2 orders of magnitude too slow and leads to tons of
false positives on our build bots due to timeouts. As it is, the
cost-benefit ratio is far too low.

The whole approach needs to be changed: Instead of trying to exhaust
some search space in unit tests, this should be turned into a fuzzing
test where only a small but random number of things are tested. The
exhaustive approach can be done separately, but definitely not in the
unit tests.

BUG=v8:3707

[Sven Panne, 2014-11-26 07:32:41]

svenpanne@chromium.org changed reviewers:
+ bmeurer@chromium.org

[Benedikt Meurer, 2014-11-26 07:46:57]

The CQ bit was checked by bmeurer@chromium.org

[Benedikt Meurer, 2014-11-26 07:46:57]

lgtm

[commit-bot: I haz the power, 2014-11-26 07:47:41]

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

[commit-bot: I haz the power, 2014-11-26 08:15:52]

Committed patchset #1 (id:1)