[test] Fix mjsunit/getters-on-elements to reset function state

[test] Fix mjsunit/getters-on-elements to reset function state

The function "foo" in "base_getter_test" was picking up a left-over
optimised code object from foo's code map, the third time that
base_getter_test was run, instead of optimising it itself. This
broke the assumptions of the test, that each case was functionally
independent from the others, and had started off with empty feedback
and no optimised code.

This breaks the test though, so we have to blacklist it pending a fix
to the root cause (http://crbug.com/v8/6101).

Review-Url: https://codereview.chromium.org/2750623004
Cr-Commit-Position: refs/heads/master@{#43828}
Committed: https://chromium.googlesource.com/v8/v8/+/2b1ed9446455ba354783af288eb4d3bf510f7cc1

[Leszek Swirski, 2017-03-15 12:02:11]

The CQ bit was checked by leszeks@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-03-15 12:02:13]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Leszek Swirski, 2017-03-15 12:03:23]

Description was changed from

==========
[test] Fix mjsunit/getters-on-elements to reset function state

The function "foo" in "base_getter_test" was picking up a left-over
optimised code object from foo's code map, the third time that
base_getter_test was run, instead of optimising it itself. This
broke the assumptions of the test, that each case was functionally
independent from the others, and had started off with empty feedback
and no optimised code.

WIP: This breaks the test though, so we'll have to blacklist it.
==========

to

==========
[test] Fix mjsunit/getters-on-elements to reset function state

The function "foo" in "base_getter_test" was picking up a left-over
optimised code object from foo's code map, the third time that
base_getter_test was run, instead of optimising it itself. This
broke the assumptions of the test, that each case was functionally
independent from the others, and had started off with empty feedback
and no optimised code.

This breaks the test though, so we have to blacklist it pending a fix
to the root cause (http://crbug.com/v8/6101).
==========

[commit-bot: I haz the power, 2017-03-15 12:28:10]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-15 12:28:11]

Dry run: This issue passed the CQ dry run.

[Leszek Swirski, 2017-03-15 12:29:18]

leszeks@chromium.org changed reviewers:
+ mvstanton@chromium.org

[Leszek Swirski, 2017-03-15 12:29:19]

Hi Mike,
this is the logic issue we discussed in that test. Shall we push this logic fix
in along with the blacklisting, pending a more thorough investigation? This is
blocking the concurrent optimisation marking, so I'd like to get it in
reasonably fast.

Ross: fyi.

[mvstanton, 2017-03-15 13:19:30]

Yep, sounds good. LGTM.

[Leszek Swirski, 2017-03-15 13:27:59]

The CQ bit was checked by leszeks@chromium.org

[commit-bot: I haz the power, 2017-03-15 13:28:06]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-15 13:31:01]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1489584479056900,
"parent_rev": "16796914cb2745bfa90e76fdb280bcf97589610c", "commit_rev":
"2b1ed9446455ba354783af288eb4d3bf510f7cc1"}

[commit-bot: I haz the power, 2017-03-15 13:31:06]

Description was changed from

==========
[test] Fix mjsunit/getters-on-elements to reset function state

The function "foo" in "base_getter_test" was picking up a left-over
optimised code object from foo's code map, the third time that
base_getter_test was run, instead of optimising it itself. This
broke the assumptions of the test, that each case was functionally
independent from the others, and had started off with empty feedback
and no optimised code.

This breaks the test though, so we have to blacklist it pending a fix
to the root cause (http://crbug.com/v8/6101).
==========

to

==========
[test] Fix mjsunit/getters-on-elements to reset function state

The function "foo" in "base_getter_test" was picking up a left-over
optimised code object from foo's code map, the third time that
base_getter_test was run, instead of optimising it itself. This
broke the assumptions of the test, that each case was functionally
independent from the others, and had started off with empty feedback
and no optimised code.

This breaks the test though, so we have to blacklist it pending a fix
to the root cause (http://crbug.com/v8/6101).

Review-Url: https://codereview.chromium.org/2750623004
Cr-Commit-Position: refs/heads/master@{#43828}
Committed:
https://chromium.googlesource.com/v8/v8/+/2b1ed9446455ba354783af288eb4d3bf510...
==========

[commit-bot: I haz the power, 2017-03-15 13:31:08]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/v8/v8/+/2b1ed9446455ba354783af288eb4d3bf510...