All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=705470

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyxQELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IpYBQ2hyb21pdW1QZXJmL2Nocm9taXVtLXJlbC1tYWMxMS1haXIvc3lzdGVtX2hlYWx0aC5jb21tb25fZGVza3RvcC90aW1lVG9GaXJzdENvbnRlbnRmdWxQYWludF9hdmcvbG9uZ19ydW5uaW5nX3Rvb2xzL2xvbmdfcnVubmluZ190b29sc19nbWFpbC1mb3JlZ3JvdW5kDAsSDVN0b3BwYWdlQWxlcnQY84wbDA


Bot(s) for this bug's original alert(s):

chromium-rel-mac11-air

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983977510557187504

=== BISECT JOB RESULTS ===
NO Test failure found

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : timeToFirstContentfulPaint_avg/long_running_tools/long_running_tools_gmail-foreground

Revision             Exit Code      N
chromium@444019      1 +- N/A       20      good
chromium@444066      1 +- N/A       20      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=long.running.tools.gmail.foreground system_health.common_desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983977510557187504

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5269872621125632


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

charliea, could you take a look?
The test does not report any results, but it works correctly regarding to the bisect result of #4.

It turns out this was because the Mac bot that this benchmark was running on had to be taken offline due to a bulging battery. This should be resolved now.