Tame mjsunit/fast-literal after fixing allocations.

Not that allocations go through Heap::AllocateRaw and actually respect
the allocation timeout, the runtime of this test spiked. This adjusts
the limit to sane values now that the values are actually respected.

R=mvstanton@chromium.org
TEST=mjsunit/fast-literal

Review URL: https://codereview.chromium.org/63603009

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17615 ce2b1a6d-e550-0410-aec6-3dcde31c8c00

diff --git a/test/mjsunit/fast-literal.js b/test/mjsunit/fast-literal.js
index 822d906..8e53244 100644 (file)
--- a/test/mjsunit/fast-literal.js
+++ b/test/mjsunit/fast-literal.js
@@ -27,14 +27,14 @@
 
 // Flags: --allow-natives-syntax --no-inline-new --nouse-allocation-folding
 
-%SetAllocationTimeout(10, 0);
+%SetAllocationTimeout(20, 0);
 function f() {
   return [[1, 2, 3], [1.1, 1.2, 1.3], [[], [], []]];
 }
 
 f(); f(); f();
 %OptimizeFunctionOnNextCall(f);
-for (var i=0; i<1000; i++) {
+for (var i=0; i<50; i++) {
   f();
 }