Allocator cleanup: remove reundant tc_set_new_mode in ProcessMemoryTest

Allocator cleanup: remove reundant tc_set_new_mode in ProcessMemoryTest

Leftover from the previous cleanups.
Previously, when base did pretend to not know anything about allocator,
tc_set_new_mode was invoked by the content layer (in content_main).
But this required this base unittest to mimic the same content behavior.

These days, instead, tc_set_new_mode() is called by base's
EnableTerminationOnOutOfMemory(). This test is already invoking
EnableTerminationOnOutOfMemory() in its initialization, so there is
no need to perform a 2nd call to tc_set_new_mode.

Also this makes the code in this test conceptually cleaner and smaller.

BUG=564618
TEST=base_unittests

Committed: https://crrev.com/e9da717d1cd3fd4b41b04456b9e454c5c028cac3
Cr-Commit-Position: refs/heads/master@{#374750}

[Primiano Tucci (use gerrit), 2016-02-10 15:55:57]

Description was changed from

==========
Allocator cleanup: remove reundant tc_set_new_mode in ProcessMemoryTest

Leftover from the previous cleanups.
Previously, when base did pretend to not know anything about allocator,
tc_set_new_mode was invoked by the content layer (in content_main).
But this required this base unittest to mimic the same content behavior.

These days, instead, tc_set_new_mode() is called by base's
EnableTerminationOnOutOfMemory(). This test is already invoking
EnableTerminationOnOutOfMemory() in its initialization, so there is
no need to perform a 2nd call to tc_set_new_mode.

Also this makes the code in this test conceptually cleaner and smaller.

BUG=564618
==========

to

==========
Allocator cleanup: remove reundant tc_set_new_mode in ProcessMemoryTest

Leftover from the previous cleanups.
Previously, when base did pretend to not know anything about allocator,
tc_set_new_mode was invoked by the content layer (in content_main).
But this required this base unittest to mimic the same content behavior.

These days, instead, tc_set_new_mode() is called by base's
EnableTerminationOnOutOfMemory(). This test is already invoking
EnableTerminationOnOutOfMemory() in its initialization, so there is
no need to perform a 2nd call to tc_set_new_mode.

Also this makes the code in this test conceptually cleaner and smaller.

BUG=564618
TEST=base_unittests
==========

[Primiano Tucci (use gerrit), 2016-02-10 16:00:47]

primiano@chromium.org changed reviewers:
+ thakis@chromium.org

[Primiano Tucci (use gerrit), 2016-02-10 16:00:47]

Nico, small cleanup.
12 shy lines in base were trying to avoid the flame-throwing, tsk.

[Primiano Tucci (use gerrit), 2016-02-10 18:24:56]

On 2016/02/10 16:00:47, Primiano Tucci wrote:
> Nico, small cleanup.
> 12 shy lines in base were trying to avoid the flame-throwing, tsk.

Leaving the office, feel free to tick if LGTY.

[Primiano Tucci (use gerrit), 2016-02-10 22:03:01]

primiano@chromium.org changed reviewers:
+ thestig@chromium.org

[Primiano Tucci (use gerrit), 2016-02-10 22:03:01]

Timezone change, let's see if I'm are luckier with +thestig.
PTAL it's a -12 lines CL

[Nico, 2016-02-10 22:04:15]

The CQ bit was checked by thakis@chromium.org

[Nico, 2016-02-10 22:04:16]

lgtm

[commit-bot: I haz the power, 2016-02-10 22:10:23]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1683153002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1683153002/1

[commit-bot: I haz the power, 2016-02-10 22:18:21]

Description was changed from

==========
Allocator cleanup: remove reundant tc_set_new_mode in ProcessMemoryTest

Leftover from the previous cleanups.
Previously, when base did pretend to not know anything about allocator,
tc_set_new_mode was invoked by the content layer (in content_main).
But this required this base unittest to mimic the same content behavior.

These days, instead, tc_set_new_mode() is called by base's
EnableTerminationOnOutOfMemory(). This test is already invoking
EnableTerminationOnOutOfMemory() in its initialization, so there is
no need to perform a 2nd call to tc_set_new_mode.

Also this makes the code in this test conceptually cleaner and smaller.

BUG=564618
TEST=base_unittests
==========

to

==========
Allocator cleanup: remove reundant tc_set_new_mode in ProcessMemoryTest

Leftover from the previous cleanups.
Previously, when base did pretend to not know anything about allocator,
tc_set_new_mode was invoked by the content layer (in content_main).
But this required this base unittest to mimic the same content behavior.

These days, instead, tc_set_new_mode() is called by base's
EnableTerminationOnOutOfMemory(). This test is already invoking
EnableTerminationOnOutOfMemory() in its initialization, so there is
no need to perform a 2nd call to tc_set_new_mode.

Also this makes the code in this test conceptually cleaner and smaller.

BUG=564618
TEST=base_unittests
==========

[commit-bot: I haz the power, 2016-02-10 22:18:22]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-16 22:31:45]

Description was changed from

==========
Allocator cleanup: remove reundant tc_set_new_mode in ProcessMemoryTest

Leftover from the previous cleanups.
Previously, when base did pretend to not know anything about allocator,
tc_set_new_mode was invoked by the content layer (in content_main).
But this required this base unittest to mimic the same content behavior.

These days, instead, tc_set_new_mode() is called by base's
EnableTerminationOnOutOfMemory(). This test is already invoking
EnableTerminationOnOutOfMemory() in its initialization, so there is
no need to perform a 2nd call to tc_set_new_mode.

Also this makes the code in this test conceptually cleaner and smaller.

BUG=564618
TEST=base_unittests
==========

to

==========
Allocator cleanup: remove reundant tc_set_new_mode in ProcessMemoryTest

Leftover from the previous cleanups.
Previously, when base did pretend to not know anything about allocator,
tc_set_new_mode was invoked by the content layer (in content_main).
But this required this base unittest to mimic the same content behavior.

These days, instead, tc_set_new_mode() is called by base's
EnableTerminationOnOutOfMemory(). This test is already invoking
EnableTerminationOnOutOfMemory() in its initialization, so there is
no need to perform a 2nd call to tc_set_new_mode.

Also this makes the code in this test conceptually cleaner and smaller.

BUG=564618
TEST=base_unittests

Committed: https://crrev.com/e9da717d1cd3fd4b41b04456b9e454c5c028cac3
Cr-Commit-Position: refs/heads/master@{#374750}
==========

[commit-bot: I haz the power, 2016-02-16 22:31:45]

Patchset 1 (id:??) landed as
https://crrev.com/e9da717d1cd3fd4b41b04456b9e454c5c028cac3
Cr-Commit-Position: refs/heads/master@{#374750}