benchmark_health_report: Query anomalies by benchmark/master.

dashboard/dashboard/benchmark_health_report_test.py

Index: dashboard/dashboard/benchmark_health_report_test.py
diff --git a/dashboard/dashboard/benchmark_health_report_test.py b/dashboard/dashboard/benchmark_health_report_test.py
index 589f34aa516ebdb3f9eba3c7a8c7b36c5cc3772d..bb4d55f4d36f08477c4cbc9d7fe2dd93d813a79d 100644
--- a/dashboard/dashboard/benchmark_health_report_test.py
+++ b/dashboard/dashboard/benchmark_health_report_test.py
@@ -126,7 +126,7 @@ class BenchmarkHealthReportTest(testing_common.TestCase):
     self._AddTests()
     response = self.testapp.post(
         '/benchmark_health_report', {
-            'benchmark': 'page_cycler',
+            'benchmark': 'speedometer',

[sullivan, 2017/02/23 03:32:25]

The previous code was able to figure out that since the first monitored
page_cycler timeseries was monitored just for CrOS, it's not monitored on the
ChromiumPerf master. But this didn't work correctly in all cases, it just
checked the first set of monitored series. The new code is more consistent.

             'num_days': '30',
             'master': 'ChromiumPerf',
         })