[test] Avoid stack space exhaustion in test by passing --no-lazy

The test depends on tricky stack space requirements, so it stopped
working in some configurations win FLAG_min_preparse_length was removed
in commit 4a5b7e32c4.

As a workaround, pass --no-lazy until the test can be refined to work
on all configurations.

BUG=v8:5729
TBR=marja@chromium.org

Review-Url: https://codereview.chromium.org/2596673002
Cr-Commit-Position: refs/heads/master@{#41878}

test/mjsunit/big-array-literal.js

@@ -28,6 +28,11 @@
 // On MacOS X 10.7.5, this test needs a stack size of at least 788 kBytes.
 // On PPC64, this test needs a stack size of at least 698 kBytes.
 // Flags: --stack-size=1000
+//
+// The above stack limits were written assuming no lazy parsing, so turn
+// off lazy parsing for this test.
+// See https://bugs.chromium.org/p/v8/issues/detail?id=5729 for details.
+// Flags: --no-lazy
 
 // Test that we can make large object literals that work.
 // Also test that we can attempt to make even larger object literals without