Comment #3 on issue 3707 by [email protected]: Several slow tests in
cctest/test-parsing
https://code.google.com/p/v8/issues/detail?id=3707#c3
The following revision refers to this bug:
https://chromium.googlesource.com/v8/v8.git/+/fd13969ef0df98e87c7f32cbb7b9f2963f4480f5
commit fd13969ef0df98e87c7f32cbb7b9f2963f4480f5
Author: svenpanne <[email protected]>
Date: Wed Nov 26 08:15:46 2014
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
Review URL: https://codereview.chromium.org/762743002
Cr-Commit-Position: refs/heads/master@{#25510}
[modify]
http://crrev.com/fd13969ef0df98e87c7f32cbb7b9f2963f4480f5/test/cctest/test-parsing.cc
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
