Reviewers: Mads Ager,
Message:
More boredom :-)
The combination of --gc-greedy and --verify-heap made greedy.js timeout on
x64
in debug mode, regardless of how much actual work is being done in the test.
If the whole point of the test is to test those two flags together, then
this CL
is obviously a bad idea. But if we can live without --verify-heap, this
fixes
the timeout. What do you think?
Description:
Fix timeout of test greedy.js
TEST=greedy.js no longer times out on x64 in debug mode
Please review this at http://codereview.chromium.org/6991011/
SVN Base: https://v8.googlecode.com/svn/branches/bleeding_edge
Affected files:
M test/mjsunit/greedy.js
Index: test/mjsunit/greedy.js
diff --git a/test/mjsunit/greedy.js b/test/mjsunit/greedy.js
index
d357f0cad373709b1a9bd0e1edaa565879194a01..8c49e41b9c6d43cb1c8ca1987f9d92899a6cb059
100644
--- a/test/mjsunit/greedy.js
+++ b/test/mjsunit/greedy.js
@@ -25,7 +25,7 @@
// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-// Flags: --gc-greedy
+// Flags: --gc-greedy --noverify-heap
function IterativeFib(n) {
var f0 = 0, f1 = 1;
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
