[system-health] Disable {load, browse}:news:washingtonpost on mobile

[system-health] Disable {load, browse}:news:washingtonpost on mobile

Rationale: The stories are failing in system_health.memory_mobile and
v8.browsing_mobile benchmarks on Android One and Nexus 5 bots.

The issue was originally addressed by completely disabling
system_health.memory_mobile on Android One. This patch undoes that, i.e.
system_health.memory_mobile will be re-enabled on Android One.

BUG=634112
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq

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

[petrcermak, 2016-08-05 12:35:01]

Description was changed from

==========
[system-health] Disable {load, browse}:news:washingtonpost on mobile

Rationale: The stories are failing in system_health.memory_mobile and
v8.browsing_mobile benchmarks on Android One and Nexus 5 bots.

The issue was originally addressed by completely disabling
system_health.memory_mobile on Android One. This patch undoes that, i.e.
system_health.memory_mobile will be re-enabled on Android One.

BUG=634112
==========

to

==========
[system-health] Disable {load, browse}:news:washingtonpost on mobile

Rationale: The stories are failing in system_health.memory_mobile and
v8.browsing_mobile benchmarks on Android One and Nexus 5 bots.

The issue was originally addressed by completely disabling
system_health.memory_mobile on Android One. This patch undoes that, i.e.
system_health.memory_mobile will be re-enabled on Android One.

BUG=634112
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

[petrcermak, 2016-08-05 12:35:32]

petrcermak@chromium.org changed reviewers:
+ nednguyen@google.com, ulan@chromium.org

[petrcermak, 2016-08-05 12:35:32]

PTAL.

Thanks,
Petr

[ulan, 2016-08-05 12:37:43]

Thank you for preparing CL. LGTM.

[petrcermak, 2016-08-05 12:40:23]

The CQ bit was checked by petrcermak@chromium.org

[commit-bot: I haz the power, 2016-08-05 12:40:47]

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

[nednguyen, 2016-08-05 13:17:40]

lgtm

[commit-bot: I haz the power, 2016-08-05 14:41:27]

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

[commit-bot: I haz the power, 2016-08-05 14:41:28]

Try jobs failed on following builders:
  android_s5_perf_cq on master.tryserver.chromium.perf (JOB_TIMED_OUT, no build
URL)

[nednguyen, 2016-08-05 14:46:17]

The CQ bit was checked by nednguyen@google.com

[commit-bot: I haz the power, 2016-08-05 14:46:38]

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

[petrcermak, 2016-08-05 16:05:13]

Description was changed from

==========
[system-health] Disable {load, browse}:news:washingtonpost on mobile

Rationale: The stories are failing in system_health.memory_mobile and
v8.browsing_mobile benchmarks on Android One and Nexus 5 bots.

The issue was originally addressed by completely disabling
system_health.memory_mobile on Android One. This patch undoes that, i.e.
system_health.memory_mobile will be re-enabled on Android One.

BUG=634112
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

to

==========
[system-health] Disable {load, browse}:news:washingtonpost on mobile

Rationale: The stories are failing in system_health.memory_mobile and
v8.browsing_mobile benchmarks on Android One and Nexus 5 bots.

The issue was originally addressed by completely disabling
system_health.memory_mobile on Android One. This patch undoes that, i.e.
system_health.memory_mobile will be re-enabled on Android One.

BUG=634112
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

[petrcermak, 2016-08-05 16:05:19]

The CQ bit was unchecked by petrcermak@chromium.org

[petrcermak, 2016-08-05 16:05:23]

The CQ bit was checked by petrcermak@chromium.org

[commit-bot: I haz the power, 2016-08-05 16:05:30]

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, 2016-08-05 16:09:28]

Description was changed from

==========
[system-health] Disable {load, browse}:news:washingtonpost on mobile

Rationale: The stories are failing in system_health.memory_mobile and
v8.browsing_mobile benchmarks on Android One and Nexus 5 bots.

The issue was originally addressed by completely disabling
system_health.memory_mobile on Android One. This patch undoes that, i.e.
system_health.memory_mobile will be re-enabled on Android One.

BUG=634112
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

to

==========
[system-health] Disable {load, browse}:news:washingtonpost on mobile

Rationale: The stories are failing in system_health.memory_mobile and
v8.browsing_mobile benchmarks on Android One and Nexus 5 bots.

The issue was originally addressed by completely disabling
system_health.memory_mobile on Android One. This patch undoes that, i.e.
system_health.memory_mobile will be re-enabled on Android One.

BUG=634112
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

[commit-bot: I haz the power, 2016-08-05 16:09:30]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-05 16:10:42]

Description was changed from

==========
[system-health] Disable {load, browse}:news:washingtonpost on mobile

Rationale: The stories are failing in system_health.memory_mobile and
v8.browsing_mobile benchmarks on Android One and Nexus 5 bots.

The issue was originally addressed by completely disabling
system_health.memory_mobile on Android One. This patch undoes that, i.e.
system_health.memory_mobile will be re-enabled on Android One.

BUG=634112
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

to

==========
[system-health] Disable {load, browse}:news:washingtonpost on mobile

Rationale: The stories are failing in system_health.memory_mobile and
v8.browsing_mobile benchmarks on Android One and Nexus 5 bots.

The issue was originally addressed by completely disabling
system_health.memory_mobile on Android One. This patch undoes that, i.e.
system_health.memory_mobile will be re-enabled on Android One.

BUG=634112
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq

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

[commit-bot: I haz the power, 2016-08-05 16:10:43]

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