Skip regress-trap-allocation-memento in gc_stress

Skip regress-trap-allocation-memento in gc_stress

This test requires its objects to live in new space, so running it
through gc stress runs just makes it susceptible to flakiness, as
was recently seen when turning on the --harmony-string-padding
flag (which just adds an extra JS file to the bootstrapper sequence).

TBR=ishell@chromium.org, jkummerow@chromium.org

Review-Url: https://codereview.chromium.org/2597543002 .
Cr-Commit-Position: refs/heads/master@{#41876}
Committed: https://chromium.googlesource.com/v8/v8/+/75586d3d9ba33ece2f0311911aa0868e4477ef84

[adamk, 2016-12-20 23:07:33]

Description was changed from

==========
Skip regress-trap-allocation-memento in gc_stress

This test requires its objects to live in new space, so running it
through gc stress runs just makes it flaky.

TBR=ishell@chromium.org, jkummerow@chromium.org
==========

to

==========
Skip regress-trap-allocation-memento in gc_stress

This test requires its objects to live in new space, so running it
through gc stress runs just makes it susceptible to flakiness, as
was recently seen when turning on the --harmony-string-padding
flag (which just adds an extra JS file to the bootstrapper sequence).

TBR=ishell@chromium.org, jkummerow@chromium.org
==========

[adamk, 2016-12-20 23:09:24]

Description was changed from

==========
Skip regress-trap-allocation-memento in gc_stress

This test requires its objects to live in new space, so running it
through gc stress runs just makes it susceptible to flakiness, as
was recently seen when turning on the --harmony-string-padding
flag (which just adds an extra JS file to the bootstrapper sequence).

TBR=ishell@chromium.org, jkummerow@chromium.org
==========

to

==========
Skip regress-trap-allocation-memento in gc_stress

This test requires its objects to live in new space, so running it
through gc stress runs just makes it susceptible to flakiness, as
was recently seen when turning on the --harmony-string-padding
flag (which just adds an extra JS file to the bootstrapper sequence).

TBR=ishell@chromium.org, jkummerow@chromium.org

Review-Url: https://codereview.chromium.org/2597543002 .
Cr-Commit-Position: refs/heads/master@{#41876}
Committed:
https://chromium.googlesource.com/v8/v8/+/75586d3d9ba33ece2f0311911aa0868e447...
==========

[adamk, 2016-12-20 23:09:25]

Committed patchset #2 (id:20001) manually as
75586d3d9ba33ece2f0311911aa0868e4477ef84 (presubmit successful).

[Igor Sheludko, 2016-12-20 23:11:36]

lgtm

[jungshik at Google, 2016-12-21 06:11:47]

On 2016/12/20 23:09:25, adamk wrote:
> Committed patchset #2 (id:20001) manually as
> 75586d3d9ba33ece2f0311911aa0868e4477ef84 (presubmit successful).

Thanks Adam ! The same thing happened when I moved --icu_case_mapping to
Harmnoy_shipping. (it also adds an extra JS file to bootstrapper sequence).