[tools/perf] Re-enable browse:news:washingtonpost (keep disabled on CQ)

[tools/perf] Re-enable browse:news:washingtonpost (keep disabled on CQ)

Enable again the benchmark to get data on perf bots, but keep disabled
on CQ while flakiness is investigated.

BUG=688190
Review-Url: https://codereview.chromium.org/2750533002
Cr-Commit-Position: refs/heads/master@{#456391}
Committed: https://chromium.googlesource.com/chromium/src/+/6b2ad995d80a7a2b1f4ae9fde3fdade1c6319f15

[perezju, 2017-03-13 12:44:07]

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

[perezju, 2017-03-13 12:44:07]

https://codereview.chromium.org/2750533002/diff/1/tools/perf/benchmarks/syste...
File tools/perf/benchmarks/system_health_smoke_test.py (right):

https://codereview.chromium.org/2750533002/diff/1/tools/perf/benchmarks/syste...
tools/perf/benchmarks/system_health_smoke_test.py:34: _DISABLED_TESTS =
frozenset({
side question: do we really want all of these long strings here? Could we factor
out the (probably always will be) common
"benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest" prefix?

[nednguyen, 2017-03-13 12:47:38]

lgtm

https://codereview.chromium.org/2750533002/diff/1/tools/perf/benchmarks/syste...
File tools/perf/benchmarks/system_health_smoke_test.py (right):

https://codereview.chromium.org/2750533002/diff/1/tools/perf/benchmarks/syste...
tools/perf/benchmarks/system_health_smoke_test.py:34: _DISABLED_TESTS =
frozenset({
On 2017/03/13 12:44:07, perezju wrote:
> side question: do we really want all of these long strings here? Could we
factor
> out the (probably always will be) common
> "benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest" prefix?

I intentionally make this so that Chromium sheriff won't be confused about how
to disable these tests. (failing test shows the full string)

[perezju, 2017-03-13 12:54:45]

The CQ bit was checked by perezju@chromium.org

[commit-bot: I haz the power, 2017-03-13 12:54:52]

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-13 14:15:57]

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

[commit-bot: I haz the power, 2017-03-13 14:15:58]

Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[perezju, 2017-03-13 14:44:52]

The CQ bit was checked by perezju@chromium.org

[commit-bot: I haz the power, 2017-03-13 14:45:04]

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-13 16:05:23]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1489416292471280, "parent_rev":
"567ff79ca421beccab0b5babdeef3d6d9b89b9ea", "commit_rev":
"6b2ad995d80a7a2b1f4ae9fde3fdade1c6319f15"}

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

Description was changed from

==========
[tools/perf] Re-enable browse:news:washingtonpost (keep disabled on CQ)

Enable again the benchmark to get data on perf bots, but keep disabled
on CQ while flakiness is investigated.

BUG=688190
==========

to

==========
[tools/perf] Re-enable browse:news:washingtonpost (keep disabled on CQ)

Enable again the benchmark to get data on perf bots, but keep disabled
on CQ while flakiness is investigated.

BUG=688190

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

[commit-bot: I haz the power, 2017-03-13 16:06:04]

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