Tame mjsunit/fast-literal after fixing allocations.
authormstarzinger@chromium.org <mstarzinger@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 11 Nov 2013 10:22:46 +0000 (10:22 +0000)
committermstarzinger@chromium.org <mstarzinger@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 11 Nov 2013 10:22:46 +0000 (10:22 +0000)
commitc6841f11803e10a3a48d87b972205d3f267cae86
treedf5510e1411cfdd7bca1a26cb83bd44773233f91
parentf681608d32967dd9db504d4fbc5c959e77e20c7a
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
test/mjsunit/fast-literal.js