GitLab

heap: Fix tests that expect write barriers for source objects on stack

The write barrier doesn't have to be triggered when a source object is
allocated on stack. The future implementation of the write barrier (with
generational heap in mind) will bailout if the source object is on
stack. This CL fixes tests that expect write barriers to be triggered
for source objects on stack.

Bug: 1029379
Change-Id: I5f8849c44bb42d42a472a9a8e8cab4f1eab6beef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2094301
Commit-Queue: Anton Bikineev <bikineev@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#748225}