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

=== Auto-CCing suspected CL author palmer@chromium.org ===

Hi palmer@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Test failure found with culprit

Suspected Commit
  Author : Chris Palmer
  Commit : dc5edc9c05901feeac616c075d0337e634f3a02a
  Date   : Sat Sep 23 21:59:41 2017
  Subject: Serialize struct tm in a safe way.

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : system_health.common_desktop
  Metric       : after_load:power_max/browse_news/browse_news_nytimes

Revision             Exit Code      N
chromium@503942      1 +- N/A       20      good
chromium@503945      1 +- N/A       20      good
chromium@503947      1 +- N/A       20      good
chromium@503948      0 +- 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=browse.news.nytimes system_health.common_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966576988102515216


For feedback, file a bug with component Speed>Bisection

Linux sandboxing code doesn't run on macOS, so I don't think it's the true culprit.

We no longer have these builders.