Move memory.long_running_dual_browser_test benchmark to tools/perf/contrib/

Move memory.long_running_dual_browser_test benchmark to tools/perf/contrib/

Since this benchmark is not scheduled on perf waterfall, we move it to the contrib/
directory & set memory-infra as OWNERS.

BUG=720257
Review-Url: https://codereview.chromium.org/2874033005
Cr-Commit-Position: refs/heads/master@{#472181}
Committed: https://chromium.googlesource.com/chromium/src/+/6ceca38dd2d95271e9fbce453e26b651e57631a0

[nednguyen, 2017-05-11 20:13:47]

nednguyen@google.com changed reviewers:
+ hjd@chromium.org, perezju@chromium.org, primiano@chromium.org

[nednguyen, 2017-05-11 20:14:38]

Description was changed from

==========
Move memory.long_running_dual_browser_test benchmark to tools/perf/contrib/

BUG=720257
==========

to

==========
Move memory.long_running_dual_browser_test benchmark to tools/perf/contrib/

Since this benchmark is not scheduled on perf waterfall, we move it to the
contrib/
directory & set memory-infra as OWNERS.

BUG=720257
==========

[nednguyen, 2017-05-11 20:14:50]

The CQ bit was checked by nednguyen@google.com to run a CQ dry run

[commit-bot: I haz the power, 2017-05-11 20:15:26]

Dry run: 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-05-11 20:36:05]

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

[commit-bot: I haz the power, 2017-05-11 20:36:06]

Dry run: Try jobs failed on following builders:
  chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[perezju, 2017-05-12 08:39:44]

This looks fine, but wait for me to do the needed changes on internal to bots to
keep it running.

[nednguyen(REVIEW IN OTHER ACC), 2017-05-12 08:41:17]

On 2017/05/12 08:39:44, perezju wrote:
> This looks fine, but wait for me to do the needed changes on internal to bots
to
> keep it running.

I expect you not need to do anything in internal bots, except maybe remove
"--also-run-disabled"?

[perezju, 2017-05-16 14:05:03]

On 2017/05/12 08:41:17, nednguyen(REVIEW IN OTHER ACC) wrote:
> On 2017/05/12 08:39:44, perezju wrote:
> > This looks fine, but wait for me to do the needed changes on internal to
bots
> to
> > keep it running.
> 
> I expect you not need to do anything in internal bots, except maybe remove
> "--also-run-disabled"?

lgtm

Yep, I thought the command needed to run the benchmark might change. But I see
that is not the case.

[nednguyen, 2017-05-16 14:07:42]

The CQ bit was checked by nednguyen@google.com

[commit-bot: I haz the power, 2017-05-16 14:08:25]

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-05-16 19:29:16]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1494943662794450, "parent_rev":
"1fb662149d40ec4b4a19d984007528ea0b8798e3", "commit_rev":
"6ceca38dd2d95271e9fbce453e26b651e57631a0"}

[commit-bot: I haz the power, 2017-05-16 19:29:32]

Description was changed from

==========
Move memory.long_running_dual_browser_test benchmark to tools/perf/contrib/

Since this benchmark is not scheduled on perf waterfall, we move it to the
contrib/
directory & set memory-infra as OWNERS.

BUG=720257
==========

to

==========
Move memory.long_running_dual_browser_test benchmark to tools/perf/contrib/

Since this benchmark is not scheduled on perf waterfall, we move it to the
contrib/
directory & set memory-infra as OWNERS.

BUG=720257

Review-Url: https://codereview.chromium.org/2874033005
Cr-Commit-Position: refs/heads/master@{#472181}
Committed:
https://chromium.googlesource.com/chromium/src/+/6ceca38dd2d95271e9fbce453e26...
==========

[commit-bot: I haz the power, 2017-05-16 19:29:33]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/6ceca38dd2d95271e9fbce453e26...