Allocation site tests aren't compatible with GcStress mode.

Allocation site tests aren't compatible with GcStress mode.

They make assumptions about elementskind of arrays based on allocation site
feedback. This feedback is highly dependent on mementos, unrooted objects
placed behind arrays in the heap meant to live until the next scavenge.

GcStress does many more gcs than normal, and wrecks havoc with this kind
of test.

BUG=
R=hpayer@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=16832

[mvstanton, 2013-09-19 12:46:46]

Hi Hannes, "PTAL"

[Hannes Payer (out of office), 2013-09-19 12:53:36]

https://codereview.chromium.org/23449042/diff/1/test/mjsunit/allocation-site-...
File test/mjsunit/allocation-site-info.js (right):

https://codereview.chromium.org/23449042/diff/1/test/mjsunit/allocation-site-...
test/mjsunit/allocation-site-info.js:41: %SetFlags("--gc-interval=-1")
Can you try to set the flag in the header of the test?

[Hannes Payer (out of office), 2013-09-19 13:10:13]

LGTM

[mvstanton, 2013-09-19 13:10:35]

thx!

https://codereview.chromium.org/23449042/diff/1/test/mjsunit/allocation-site-...
File test/mjsunit/allocation-site-info.js (right):

https://codereview.chromium.org/23449042/diff/1/test/mjsunit/allocation-site-...
test/mjsunit/allocation-site-info.js:41: %SetFlags("--gc-interval=-1")
On 2013/09/19 12:53:36, Hannes Payer wrote:
> Can you try to set the flag in the header of the test?

sadly no due to ordering.

[mvstanton, 2013-09-19 13:32:09]

Committed patchset #1 manually as r16832 (presubmit successful).